-
Notifications
You must be signed in to change notification settings - Fork 5
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
Nightly update pipeline using Helm deploy #50
base: main
Are you sure you want to change the base?
Conversation
e3eaae4
to
c7d6db7
Compare
Tools do not need redeploy. The helm-install-nightly pipeline can just reinstall kuadrant and keep tools deployed as they were. That needs sparation of tools deploy with |
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.
@azgabur I haven't tried yet, no real issues just a few questions. I will approve once I will try on clean cluster.
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 tried both pipelines on a clean cluster several times and it worked - meaning they finished successfully and Kuadrant was installed. LGTM
@azgabur It would be nice to squash commits ;) |
deploy/pipeline-nightly-update.yaml
Outdated
name: kube-api | ||
type: string | ||
- description: Istio deployment. Only these values 'sail', 'ossm', 'ossm3' | ||
name: istioProvider |
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.
name: istioProvider | |
name: istio-provider |
tasks/02-uninstall.yaml
Outdated
- uninstall | ||
- -n=default | ||
- --ignore-not-found | ||
- --wait | ||
- kuadrant-operators |
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.
inline commands are more readable
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 inlined the shorter commands but the helm commands are kinda long and I think it helps readability in that case. I refactored the helm commands to multi-line so maybe its better now?
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 changed the helm
commands back as they are more readable that way
tasks/01-clone.yaml
Outdated
limits: | ||
cpu: 250m | ||
memory: 128Mi | ||
image: quay.io/rhn_support_azgabur/alpine/k8s:1.31.2 |
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.
can you link a :latest image here, so we don't have to update this every time image changes?
deploy/pipeline.yaml
Outdated
name: kube-api | ||
type: string | ||
- description: Kuadrant image url | ||
name: indexImage |
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.
there is a convention for the names
name: indexImage | |
name: index-image |
tasks/01-clone.yaml
Outdated
- https://github.com/azgabur/kuadrant-helm-install | ||
- $(workspaces.shared-workspace.path)/kuadrant-helm-install | ||
command: | ||
- git |
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 using /bin/bash everywhere else for the command. I don't see a good reason to juggle between different commands and not to just use bash -c "git ..." with whatever arguments u want
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.
Changed back after discussion
tasks/01-clone.yaml
Outdated
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.
go by the convention on tasks names please e.g. clone-task.yaml, uninstall-kuadrant-task.yaml, etc.
tasks/kustomization.yaml
Outdated
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 rly want pipelines to have independent deployment if possible. Nightly and release pipelines do not require helm tasks to work, so it'll be good to not install them as a collection.
You can try an approach with differently named kustomization files, for different pipelines, or different directory for the helm tasks
Signed-off-by: Alex Zgabur <[email protected]>
40c0ce2
to
68dd606
Compare
- name: istio-provider | ||
value: ossm3 | ||
- name: kube-api | ||
value: https://kubernetes.default |
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.
The login task has problem with this url - the sed command, can it be fixed in future PR? @averevki
Signed-off-by: Alex Zgabur <[email protected]>
Now you really really can do re-review :) |
Signed-off-by: Alex Zgabur <[email protected]>
Replaces #39
Closes #41
This nightly-update-pipeline can update specified cluster to newest nightly using helm deploy.
The deploy pipeline can install any choosen Kuadrant image on specified cluster.
Done:
image
,channel
of kuadrant and maybe other variables