-
Notifications
You must be signed in to change notification settings - Fork 45
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 the Pulumi Kubernetes Operator #141
Conversation
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.
apiVersion: source.toolkit.fluxcd.io/v1beta2 | ||
kind: HelmRepository | ||
metadata: | ||
name: pulumi-kubernetes-operator |
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.
Consider naming this pulumi
rather than pulumi-kubernetes-operator
since, in concept, it could serve other charts too.
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 made this change.
apiVersion: rbac.authorization.k8s.io/v1 | ||
kind: Role | ||
metadata: | ||
name: pulumi-tester-role |
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 think it atypical for an object name to have its type as a suffix. In other words, I would name this pulumi-tester
. Likewise for the binding.
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.
Good call. I do not like smurf naming.
apiVersion: v1 | ||
kind: ConfigMap | ||
metadata: | ||
name: pulumi-tester-configmap |
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
@elamaran11 Did my best to get the |
@jkodroff Who will fix the above changes pointed by @EronWright. let me know when done i can test it. |
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.
@jkodroff One comment on the token reference.
valueFrom: | ||
secretKeyRef: | ||
name: pulumi-access-token | ||
key: value |
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.
@jkodroff This doesnt seem to match with your ExternalSecret
k8s rsource. If the key
is pulumi-access-token
, it should match.
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 believe this is now fixed.
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 would recommend giving a meaningful name like accessToken
for key.
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.
Minor feedback but i can work on the testing tomorrow.
@@ -0,0 +1 @@ | |||
kubeconfig.yml |
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.
Please remove this file.
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.
Do you mean the .gitignore
file? What is the rationale?
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.
Why do we need this .gitignore
file. We have one at root.
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.
Done
targetNamespace: pulumi | ||
chart: | ||
spec: | ||
chart: pulumi-kubernetes-operator |
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.
Should we specify a chart version, e.g. 0.3.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.
yes thats mandatory, nice catch
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.
Did you test the helm release did it work?
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 fixed this to use 0.3.*
, does that seem right @elamaran11 ?
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.
Where is the change? I dont see the version.
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.
@jkodroff @EronWright Have some feedback on the PR which needs to be fixed.
- ExternalSecret KeyName and SecretRef is not correct so the installation fails. Also having meaningful name for
secretKey
- Secret Reference in cronjob should have a meaningful name as aligned to comment 1.
data: | ||
- secretKey: pulumi-access-token # which key it's going to be stored | ||
remoteRef: | ||
key: value # Our secret-name goes here |
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 would rather have a specific name for the KVP than value
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.
secretKey
should be a something reasonable like accessToken
and key should the keyname in secrets manager which is pulumi-access-token
targetNamespace: pulumi | ||
chart: | ||
spec: | ||
chart: pulumi-kubernetes-operator |
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.
Did you test the helm release did it work?
@@ -0,0 +1,7 @@ | |||
apiVersion: v1 |
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.
If this configmap is for tester, this should be moved to Testers/Pulumi
folder.
@@ -0,0 +1,10 @@ | |||
--- | |||
apiVersion: rbac.authorization.k8s.io/v1 |
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.
If this configmap is for tester, this should be moved to Testers/Pulumi
folder.
@@ -0,0 +1,13 @@ | |||
--- | |||
apiVersion: rbac.authorization.k8s.io/v1 |
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.
If this configmap is for tester, this should be moved to Testers/Pulumi
folder.
@@ -0,0 +1,6 @@ | |||
--- |
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.
If this configmap is for tester, this should be moved to Testers/Pulumi
folder.
@@ -0,0 +1 @@ | |||
kubeconfig.yml |
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.
remove this file
Use alpine:k8s:1.26.2 image. Use kubectl wait rather than sleep.
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.
@jkodroff @EronWright I would recommend making all changes listed in the PR and also test it locally once along with sharing a screen shot on the test job working locally. Once you have it, i can proceed with testing. At this point the testing is blocked due to errors with test job secrets.
targetNamespace: pulumi | ||
chart: | ||
spec: | ||
chart: pulumi-kubernetes-operator |
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.
Where is the change? I dont see the version.
@elamaran11 Thanks for your patience, I encountered a small delay in pushing the changes, due to a permissions issue on the fork. I believe I've addressed the feedback; of course we'll discuss further once you can see them. Meanwhile, here's the local test output (tested using EKS):
|
@elamaran11 the changes have been pushed, please take another look. |
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.
@EronWright Code changes look good for both the helm deployment and the test job. I will start to test this in my lab today. Thankyou
Hi @EronWright I see the stack is created and destroyed and test job concluded successfully. This is good news. I can say my test is concluded in EKS-A Baremetal environment. I will continue my tests in other environment. jc though, i dont see the stack in the Pulumi console is it because of instant create and delete?
|
@EronWright I got to understand its instant and also i saw the same in the console for quick few seconds. The product is validated across EKS-A BareMetal, vSphere and EKS Local cluster. EKS-A Snowball is still pending, i will complete this testing today or tomorrow when i get to the lab. |
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.
Everything works fine. Congratulations and Thankyou @EronWright @jkodroff . Please continue to maintain your software for version upgrades via PRs.
Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.