-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
feat(backend): Add Semaphore and Mutex fields to Workflow CR #11370
base: master
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,29 @@ | ||
kind: ConfigMap | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think this lgtm, but I just had a thought. What happens if:
Is that down the line upgrade going to overwrite my customized configmap with this blank one? It'd be cool if we could test that somehow -- perhaps by manually creating the configmap on a cluster, putting data in it, and then installing kfp. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Makes sense. |
||
apiVersion: v1 | ||
metadata: | ||
name: semaphore-config | ||
data: {} | ||
--- | ||
apiVersion: batch/v1 | ||
kind: Job | ||
metadata: | ||
name: semaphore-configmap-init | ||
namespace: kubeflow | ||
spec: | ||
template: | ||
spec: | ||
containers: | ||
- name: create-configmap | ||
image: bitnami/kubectl:latest | ||
command: | ||
- /bin/sh | ||
- -c | ||
- | | ||
if ! kubectl get configmap semaphore-config -n kubeflow > /dev/null 2>&1; then | ||
echo "Creating semaphore-config ConfigMap..." | ||
kubectl create configmap semaphore-config -n kubeflow --from-literal=init="" | ||
else | ||
echo "ConfigMap semaphore-config already exists. Skipping creation." | ||
fi | ||
restartPolicy: OnFailure | ||
backoffLimit: 3 |
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 don't love using this Options struct for these fields, but I'm not sure what an alternative would be. I guess it's fine for now and maybe we can figure out a cleaner way down the line.