Skip to content
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.

Sign up for GitHub

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

Jump to bottom

(Addon's): addon's with version Auto not deployed #1086

Closed
FonsBiemans opened this issue Oct 21, 2024 · 2 comments · Fixed by #1089
Closed

(Addon's): addon's with version Auto not deployed #1086

FonsBiemans opened this issue Oct 21, 2024 · 2 comments · Fixed by #1089
Labels
bug Something isn't working

Comments

@FonsBiemans
Copy link

Describe the bug

i have the following Addon's: CoreDNS, Kube-proxy, EBS CSI Driver, and the VPC CNI
it the version of these addon's is set to Auto, they are not deployed to the cluster. when i set them to a specific version they are deployed.

Expected Behavior

when the version is set to auto, it should deploy the latest version.

Current Behavior

not deploying the addon, no errors, synth and deploy is going without error's but when you check the cluster, there are no addon's.

Reproduction Steps

        new blueprints.addons.CoreDnsAddOn(
           'v1.11.1-eksbuild.8'

        ),
        new blueprints.addons.KubeProxyAddOn(
          'v1.30.0-eksbuild.3'

        ),

Possible Solution

not found yet.

Additional Information/Context

No response

CDK CLI Version

2.161.1

EKS Blueprints Version

1.15.1

Node.js Version

v18.18.2

Environment details (OS name and version, etc.)

mac os, and github action ubuntu.

Other information

No response
@FonsBiemans FonsBiemans added the bug Something isn't working label Oct 21, 2024
@shapirov103
Copy link
Collaborator

Accepted, most likely related to lack of version registered for 1.30 EKS version. When running synth, do you mind making sure that you have AWS credentials configured that allow access to the aws eks describe-addon-versions API/CLI?
To detect the version we make the API call, if fails, then we make a static lookup in the internal dictionary.
I will also look into lack of diagnostics that you mentioned, you should get errors in the stdout/stderr.

@shapirov103
Copy link
Collaborator

You can set the log level like and see if you get any descriptive messages:

import { utils } from "@aws-quickstart/eks-blueprints";
import { HelmAddOn } from '@aws-quickstart/eks-blueprints';


    blueprints.HelmAddOn.validateHelmVersions = true;
    blueprints.HelmAddOn.failOnVersionValidation = false;
    utils.logger.settings.minLevel = 3; // info
    utils.userLog.settings.minLevel = 2; // debug
    
    builder...

if it works, I can enable these by default

@shapirov103 shapirov103 mentioned this issue Oct 22, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Added support for 1.31 and default EKS/k8s version is set to 1.30 aws-quickstart/cdk-eks-blueprints
2 participants
@FonsBiemans @shapirov103