New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Splunk Operator: Upgrade AWS-SDK-GO To at least v1.47.11 to enable EKS POD Identity feature #1326
Labels
Comments
stevbitmex
changed the title
Splunk Operator:
Splunk Operator: Upgrade AWS-SDK-GO To at least v1.47.11 to enable EKS POD Identity feature
Apr 26, 2024
Hello @stevbitmex we will work on this and update you |
Hi Vivekr,
Looking forward to your help on this ASAP as we're blocked to production
because of this issues
Thanks
…On Sat, Apr 27, 2024 at 1:38 AM vivekr-splunk ***@***.***> wrote:
Hello @stevbitmex <https://github.com/stevbitmex> we will work on this
and update you
—
Reply to this email directly, view it on GitHub
<#1326 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BGGH67H6FNIPY3LSMDHCIQ3Y7KNJLAVCNFSM6AAAAABG27UWOWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANZZHEZTKNJUGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
This e-mail and all information in, attached to, or linked via this
e-mail (together the 'e-mail') is confidential and may be legally
privileged. It is intended solely for the intended addressee(s). Access to,
or any onward transmission, of this e-mail by any other person is not
authorized. If you are not the intended recipient, you are requested to
immediately alert the sender of this e-mail and to immediately delete this
e-mail. Any disclosure in any form of all or part of this e-mail, or of any
the parties to it, including any copying, distribution or any action taken
or omitted to be taken in reliance on it, is prohibited and may be
unlawful.
This e-mail is not, and is not intended to be, and should not be
construed as being, (a) any offer, solicitation, or promotion of any kind;
(b) the basis of any investment or other decision(s); (c) any
recommendation to buy, sell or transact in any manner any good(s),
product(s) or service(s), nor engage in any investment(s) or other
transaction(s) or activities; or (d) the provision of, or related to, any
advisory service(s) or activities, including regarding any investment, tax,
legal, financial, accounting, consulting or any other related service(s).
Please note, US Persons <http://bitmex.com/us-person-definition> are
prohibited from accessing the services of the BitMEX trading platform. For
more information on Restricted Jurisdictions, please read our Terms of
Service <https://www.bitmex.com/terms>.
|
how it can be blocker, if it is a feature request? |
Hi @yaroslav-nakonechnikov technically, this is not a blocker as we can use role arn as alternatives. However, as we adopt EKS POD Identity as one of our security best practises. Therefore, we prefer to have this available before production |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please select the type of request
Enhancement
Tell us more
Describe the request
Issues
This is not possible because:
v1.42.16
K8s environment
Proposed changes
The text was updated successfully, but these errors were encountered: