set common cert to false
All checks were successful
continuous-integration/publish-helm Helm publish succeeded
All checks were successful
continuous-integration/publish-helm Helm publish succeeded
This commit is contained in:
25
argo-helm.yaml
Normal file
25
argo-helm.yaml
Normal file
@@ -0,0 +1,25 @@
|
|||||||
|
apiVersion: argoproj.io/v1alpha1
|
||||||
|
kind: Application
|
||||||
|
metadata:
|
||||||
|
name: amplify-fusion
|
||||||
|
namespace: openshift-gitops
|
||||||
|
spec:
|
||||||
|
project: default
|
||||||
|
destination:
|
||||||
|
server: https://kubernetes.default.svc
|
||||||
|
namespace: amplify-fusion
|
||||||
|
source:
|
||||||
|
repoURL: https://gitea.apilab.us/cscott/amplify-fusion.git
|
||||||
|
targetRevision: main
|
||||||
|
path: .
|
||||||
|
helm:
|
||||||
|
valueFiles:
|
||||||
|
- values.yaml
|
||||||
|
syncPolicy:
|
||||||
|
automated:
|
||||||
|
prune: true
|
||||||
|
selfHeal: true
|
||||||
|
syncOptions:
|
||||||
|
- CreateNamespace=true
|
||||||
|
- ApplyOutOfSyncOnly=true
|
||||||
|
- PruneLast=true
|
||||||
@@ -130,7 +130,7 @@ common:
|
|||||||
# The key reference to the cert in the domain-certificate secret. If using cert-manager, leave as 'keystore.p12'
|
# The key reference to the cert in the domain-certificate secret. If using cert-manager, leave as 'keystore.p12'
|
||||||
# To create the required secret yourself run: `kubectl create secret generic domain-certificate --from-file=keystore.p12=/path/to/cert`
|
# To create the required secret yourself run: `kubectl create secret generic domain-certificate --from-file=keystore.p12=/path/to/cert`
|
||||||
name: "keystore.p12"
|
name: "keystore.p12"
|
||||||
enabled: true
|
enabled: false
|
||||||
# Set the password for your certificate, or leave empty and create 'certificate-password' secret external to helm deployment
|
# Set the password for your certificate, or leave empty and create 'certificate-password' secret external to helm deployment
|
||||||
# A password is needed whether you create the certificate yourself or generate the secret using the cert-manager feature below
|
# A password is needed whether you create the certificate yourself or generate the secret using the cert-manager feature below
|
||||||
# 'certificate-password' secret should have 1 data entry with the key 'password'
|
# 'certificate-password' secret should have 1 data entry with the key 'password'
|
||||||
|
|||||||
Reference in New Issue
Block a user