-
Notifications
You must be signed in to change notification settings - Fork 1
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
[IBCDPE-939] Correcting some issues #6
Conversation
- name: Clone repo | ||
uses: actions/checkout@master | ||
- name: tfsec | ||
uses: aquasecurity/tfsec-pr-commenter-action@v1.2.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very neat action!
# AWS using my SSO session for the profile `dpe-prod-admin`. After authenticated | ||
# assuming that we want to use the `role/eks_admin_role` to connect to the k8s | ||
# cluster". This will update your kubeconfig with permissions to access the cluster. | ||
aws eks update-kubeconfig --region us-east-1 --name dpe-k8 --role-arn arn:aws:iam::766808016710:role/eks_admin_role --profile dpe-prod-admin |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, these instructions worked for me!
➜ ~ kubectl get namespace
NAME STATUS AGE
airflow Active 3d3h
default Active 3d18h
kube-node-lease Active 3d18h
kube-public Active 3d18h
kube-system Active 3d18h
spot-system Active 3d14h```
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔥 fantastic - great additions here. Thanks for lowering the Admin access to power user as well. This is coming together nicely!
Problem:
spotinst/kubernetes-controller/ocean
seems like it was a mistake to add thisSolution:
Testing: