-
Notifications
You must be signed in to change notification settings - Fork 419
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
add helm values for cluster controller primary access from secondary #3784
Conversation
Signed-off-by: Cliff Colvin <[email protected]>
Signed-off-by: Cliff Colvin <[email protected]>
Co-authored-by: Thomas Nguyen <[email protected]>
@mittal-ishaan I've made some modifications. I removed the net new |
@mittal-ishaan I am seeing similar results when running the following test: clusterController:
enabled: true
primaryKubecostURL: "https://kubecost.myorganization.com"
kubecostAPIKey: "1234" helm template . -f values-thomas.yaml --show-only templates/kubecost-cluster-controller-template.yaml Additionally, I've validated that the secret is only created when # primaryKubecostURL is set
$ helm template . -f values-thomas.yaml --show-only templates/kubecost-cluster-controller-template.yaml | grep "kind"
kind: ServiceAccount
kind: Secret
kind: ClusterRole
kind: ClusterRoleBinding
kind: ClusterRole
- kind: ServiceAccount
kind: Service
kind: Deployment
# primaryKubecostURL="" and kubecostAPIKey=""
helm template . -f values-thomas.yaml --show-only templates/kubecost-cluster-controller-template.yaml | grep "kind"
kind: ServiceAccount
kind: ClusterRole
kind: ClusterRoleBinding
kind: ClusterRole
- kind: ServiceAccount
kind: Service
kind: Deployment |
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.
I'm approving. @mittal-ishaan Please merge if my changes look good here.
/cherry-pick v2.6 |
…3784) * add helm values for cluster controller primary access from secondary Signed-off-by: Cliff Colvin <[email protected]> * make secret Signed-off-by: Cliff Colvin <[email protected]> * controller secret creation logic * Apply suggestions from code review Co-authored-by: Thomas Nguyen <[email protected]> * nit fix * add lycheeignore url * Move controller-secrets.yaml into the main kubecost-cluster-controller-template.yaml --------- Co-authored-by: jesse goodier <[email protected]> Co-authored-by: Thomas Nguyen <[email protected]> Co-authored-by: Ishaan Mittal <[email protected]> Co-authored-by: thomasvn <[email protected]>
…3784) (#3844) * add helm values for cluster controller primary access from secondary * make secret * controller secret creation logic * Apply suggestions from code review * nit fix * add lycheeignore url * Move controller-secrets.yaml into the main kubecost-cluster-controller-template.yaml --------- Co-authored-by: Cliff Colvin <[email protected]> Co-authored-by: jesse goodier <[email protected]> Co-authored-by: Thomas Nguyen <[email protected]> Co-authored-by: Ishaan Mittal <[email protected]> Co-authored-by: thomasvn <[email protected]>
Signed-off-by: Cliff Colvin [email protected]
What does this PR change?
Adds the ability to set primary cluster aggregator url, and define a service token/api key for access.
Does this PR rely on any other PRs?
NA
How does this PR impact users? (This is the kind of thing that goes in release notes!)
Adds ability to define url and api key for cluster-controller primary access
Links to Issues or tickets this PR addresses or fixes
What risks are associated with merging this PR? What is required to fully test this PR?
NA
How was this PR tested?
qa-eks3 for last few months
helm template from values:
give us:
Have you made an update to documentation? If so, please provide the corresponding PR.
v2.6