-
Notifications
You must be signed in to change notification settings - Fork 36
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
[SURE-3752] [EKS] Allow the managed node group warning to be cleared #301
Comments
see also rancher/dashboard#9618 |
salasberryfin
moved this from Backlog
to In Progress (5 max)
in CAPI & Hosted Kubernetes providers (EKS/AKS/GKE)
Dec 13, 2023
salasberryfin
moved this from In Progress (5 max)
to Blocked
in CAPI & Hosted Kubernetes providers (EKS/AKS/GKE)
Dec 14, 2023
salasberryfin
moved this from Blocked
to In Progress (5 max)
in CAPI & Hosted Kubernetes providers (EKS/AKS/GKE)
Dec 15, 2023
@mjura and I investigated this issue and found some relevant details:
Furthermore, the design docs state that only using managed node groups is supported in EKS. You can read about this decision here. We consider this enough to close this issue. |
github-project-automation
bot
moved this from In Progress (5 max)
to Done
in CAPI & Hosted Kubernetes providers (EKS/AKS/GKE)
Dec 18, 2023
mjura
added a commit
to mjura/rancher
that referenced
this issue
Dec 27, 2023
This was referenced Dec 27, 2023
This will be fixed in rancher/rancher#43881 |
mjura
added a commit
to mjura/rancher
that referenced
this issue
Dec 27, 2023
mjura
added a commit
to mjura/rancher
that referenced
this issue
Dec 27, 2023
Issue: rancher/eks-operator#301 (cherry picked from commit f1acaaf)
mjura
added a commit
to mjura/rancher-docs
that referenced
this issue
Dec 28, 2023
Issue: rancher/eks-operator#301 Update eks cluster configuration with section about: - Launching self-managed Amazon Linux nodes - IAM roles for service accounts
Documentation part rancher/rancher-docs#1048 |
mjura
moved this from Done
to PR to be reviewed
in CAPI & Hosted Kubernetes providers (EKS/AKS/GKE)
Dec 28, 2023
mjura
moved this from PR to be reviewed
to To Test
in CAPI & Hosted Kubernetes providers (EKS/AKS/GKE)
Jan 17, 2024
mjura
added a commit
to mjura/rancher-docs
that referenced
this issue
Jan 17, 2024
Issue: rancher/eks-operator#301 Update eks cluster configuration with section about: - Launching self-managed Amazon Linux nodes - IAM roles for service accounts
github-project-automation
bot
moved this from To Test
to Done
in CAPI & Hosted Kubernetes providers (EKS/AKS/GKE)
Jan 26, 2024
This was referenced Jan 29, 2024
martyav
added a commit
to rancher/rancher-docs
that referenced
this issue
Mar 7, 2024
* Update eks cluster configuration Issue: rancher/eks-operator#301 Update eks cluster configuration with section about: - Launching self-managed Amazon Linux nodes - IAM roles for service accounts * Apply suggestions from code review * Apply suggestions from code review * fixed bad link * versioning --------- Co-authored-by: Marty Hernandez Avedon <marty.avedon@suse.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
SURE-3752
Business case
Using self-managed node groups from a registered EKS cluster is at times preferred or desired, the warning adds an annoyance to the Rancher experience.
Request description:
Allow the warning for 'Cluster must have at least one managed nodegroup' to be cleared, or informational
Actual behavior:
Red warning is always present in the UI
Expected behavior:
When the cluster is functioning as usual, cluster-agent is deployed and there are nodes registered, the warning is unnecessary.
This could also be confirmed via the EKS API endpoint or detecting a cluster-agent tunnel connection, if it was able to be cleared this would provide a way for users to remove the warning.
Workaround:
Is workaround available and implemented? no (kind of)
What is the workaround: Add a managed node group
PR's
The text was updated successfully, but these errors were encountered: