-
Notifications
You must be signed in to change notification settings - Fork 10
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
FLPATH 1048: Extend software template to offer the CI pipeline (Tekton option) #19
Conversation
* Set default values * Add - to the workflow ID
* Set default values * Add - to the workflow ID
Using forked template
removed dev properties
clusterDomain: | ||
title: Cluster domain | ||
type: string | ||
default: cluster-jkrpp.dynamic.redhatworkshops.io |
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.
no need for a default for this field.
title: Cluster domain | ||
type: string | ||
default: cluster-jkrpp.dynamic.redhatworkshops.io | ||
description: Cluster domain |
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 in this context this cluster domain is for the tekton pipeline so it won't be mixed with being also the cluster to run the workflows?
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.
Ok, even if having workflows and tekton on different clusters is something we have never experiment so far (probably the ArgoCD will need its own cluster configuration, in this multi-cluster deployment)
Tekton
(default) andNone
Tekton
, also generates atekton
folder with the workflow templates to generate the triggering resourcesTekton
, also generates a GitHub workflow folder to deploy the resources