No topics, call cancelled.
No topics, call cancelled.
Holiday in US
No call this week.
Treasuremap Strategy to achieve Release 2
I think issues align with this somewhat : https://review.opendev.org/q/status:open±is:wip+project:airship/treasuremap+branch:v2
LABS:
ISSUES :
Use Image Builder in Treasduremap for BM Nodes …
Define BM site Type
Release 2 Target fopr Treasuremap is to satisfy (TBD) for airship-coresite type.
Following discussion of https://github.com/airshipit/airshipctl/issues/419
apiVersion: airshipit.org/v1alpha1
kind: ReplacementTransformer
metadata:
name: ......
annotations:
config.kubernetes.io/function: |-
container:
image: quay.io/airshipit/replacement-transformer:latest
Need a mechanism to specify the version for the plugin image once , and not in every ReplacementTarnsformer artifact.
Conclusion :
Tag Management for Plugins
Create Issue for Plugin Release management.
Issue :
Develop a Tool to manage updating function that are sourced from other upstream… Need to be able to identify how and where the information is gathere.
TODO : Discussion with Tigera about including the https://docs.projectcalico.org/manifests/tigera-operator.yaml as a version released artifact.
From the 11/12 Design call, identify the list of functions impacted so we can be as specific as possible when creating the issue.
[function]/upstream/
[function]/upstream/
and have a thin passthrough [function]/kustomization.yaml
Note 1: the command that was used to get the encrypted file:
sops -e -p FBC7B9E2A4F9289AC0C1D4843D16CEE4A27381B4 -e --encrypted-regex
'^(certificate-authority-data|certificate-authority-data|client-certificate-data|client-key-data)$' kubeconfig.yaml > encrypted-kubeconfig.yaml
Note 2: starting sops 3.6.1 it will be possible to do it in more unified way:
sops -e -p FBC7B9E2A4F9289AC0C1D4843D16CEE4A27381B4 -e --unencrypted-regex '^(kind|apiVersion|group|metadata|server)$' kubeconfig.yaml > encrypted-kubeconfig.yaml
need to wait for this PR to be merged or build the updated image.
airshipctl phase render –render [phase|executor|bundle]
We still have a non-read-only kubectl command in our deployment process,
to remove the master taint from the target cluster control plane prior
to pivoting from the ephemeral to target:
https://github.com/airshipit/airshipctl/blob/master/tools/deployment/31_deploy_initinfra_target_node.sh#L22-L26
Can we accomplish this declaratively, or, programmatically via airshipctl?
We also use kubectl to pause the ephemeral cluster's BMH definitions
while orchestrating a move:
https://github.com/airshipit/airshipctl/blob/master/tools/deployment/33_cluster_move_target_node.sh#L27
Can we accomplish this programmatically via airshipctl phase clusterctl-move?
Path forward with image builder integration
https://hackmd.io/6CgeJKqVQJ6vpT2DC5mx6A
Is anyone actively working https://github.com/airshipit/airshipctl/issues/248 & https://github.com/airshipit/airshipctl/issues/249
Still open questions?
https://github.com/airshipit/airshipctl/issues/323
Discussion here https://hackmd.io/3AGF1UHJTcOHHhSE0rnT9w
This should be leveraged y airshipctl to update the site level kubeconfig after the workload cluster are created or redeployed.
Identify the appropriate issue that asks for the airshipctl command.
Clearly the namespace will be predefined /declared and will be Tenant/Workload custer specific
#335
https://github.com/airshipit/airshipctl/issues/335
Discussion at https://hackmd.io/BbFyJRKGRQiuXYJduPhu4Q
Will identify SIG YAML Design Topic from the Critical list of issues https://github.com/airshipit/airshipctl/issues?q=is%3Aopen+is%3Aissue+milestone%3Av2.0++-label%3Apriority%2Fcritical+label%3A"design+needed"+
https://github.com/airshipit/airshipctl/issues/323
Discussion here https://hackmd.io/3AGF1UHJTcOHHhSE0rnT9w
https://github.com/airshipit/airshipctl/issues/317