airship
/
treasuremap
Code Issues Proposed changes

Fix controlplane-ephemeral phase catalog reference 

The controlplane-ephemeral phases in both Treasuremap sites use the
ephemeral networking catalog; however, they should use the target
cluster networking catalog since the phases are responsible for
deploying the target cluster. When using the ephemeral networking
catalog, the target cluster tries to reach the ephemeral cluster,
resulting in unsigned certificate errors.

This change updates the references to point to the target cluster
networking catalog.

Change-Id: Ie5dfdee393098d257cbc57542681a8ce3733d316
This commit is contained in:
Drew Walters 2020-11-19 00:34:32 +00:00
parent 39a6036ca8
commit 5cd850700b
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
manifests/site/test-site/ephemeral/controlplane/kustomization.yaml
View File

@ -2,7 +2,7 @@ apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
resources:
- ../../../../type/airship-core/ephemeral/controlplane
- ../catalogues
- ../../target/catalogues # NOTE: use target networking for this phase
# TODO (dukov) It's recocommended to upload BareMetalHost objects separately
# otherwise nodes will hang in 'registering' state for quite a long time
- nodes

2
manifests/site/virtual-network-cloud/ephemeral/controlplane/kustomization.yaml
View File

@ -2,7 +2,7 @@ apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
resources:
- ../../../../type/network-cloud/ephemeral/controlplane
- ../catalogues
- ../../target/catalogues # NOTE: use target networking for this phase
# TODO (dukov) It's recocommended to upload BareMetalHost objects separately
# otherwise nodes will hang in 'registering' state for quite a long time
- nodes