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.

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

Documentation about default for enable_irsa is incorrect. #2998

Open
1 task done
thehandsomezebra opened this issue Apr 3, 2024 · 3 comments
Open
1 task done

Documentation about default for enable_irsa is incorrect. #2998

thehandsomezebra opened this issue Apr 3, 2024 · 3 comments

Comments

@thehandsomezebra
Copy link

Description

enable_irsa is documented as default false BUT Actual enable_irsa is actually default true

sources for where it states false:

sources for where it states true:

If your request is for a new feature, please use the Feature request template.

  • ✋ I have searched the open/closed issues and my issue is not listed.

Versions

  • Module version [Required]: 20.8.4 (not certain if this appears in other versions, but likely it does)

Reproduction Code [Required]

Steps to reproduce the behavior:

  1. Read documentation.
  2. Expect enable_irsa to be default false and do not define it.

Expected behavior

enable_irsa is set to false.

Actual behavior

enable_irsa is set to true.

Additional context

As I am currently working on 20.8.4, I can confirm that this is here -- however I can only assume that this has persisted since 20.x has come along.

@suminhong
Copy link

Hmm well.
The default value of enable_irsa of "eks module" is true, but the default value of enable_irsa of "karpenter submodule" is only false.
The two are different.

@thehandsomezebra
Copy link
Author

Hmm well. The default value of enable_irsa of "eks module" is true, but the default value of enable_irsa of "karpenter submodule" is only false. The two are different.

Good point -- hadn't realized that at first.

I think what led me down that being a discrepancy was the upgrade notes.

Copy link

This issue has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days

@github-actions github-actions bot added the stale label May 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants