Skip to content
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

e2e: Replace Kuttl-in-Kuttl with simple kubectl apply in scripts #103

Closed
bcm820 opened this issue Feb 9, 2024 · 1 comment · Fixed by #131
Closed

e2e: Replace Kuttl-in-Kuttl with simple kubectl apply in scripts #103

bcm820 opened this issue Feb 9, 2024 · 1 comment · Fixed by #131
Labels
feature New feature or request

Comments

@bcm820
Copy link
Contributor

bcm820 commented Feb 9, 2024

The Kuttl-in-Kuttl pattern introduced in #80 can be replaced with defining a script that simply runs kubectl apply while passing dynamic data. The TestStep will fail if any of the commands exit with non-zero.

MACHINE_UID="$(OBJ=machines/machine-sample make getKubeUid)"

cat <<EOF | kubectl apply -n $NAMESPACE -f -
apiVersion: infrastructure.cluster.x-k8s.io/v1alpha1
kind: LinodeMachine
metadata:
  ownerReferences:
  - apiVersion: cluster.x-k8s.io/v1beta1
    kind: Machine
    name: machine-sample
    uid: ${MACHINE_UID}
EOF
@bcm820 bcm820 added the feature New feature or request label Feb 9, 2024
@eddycharly
Copy link
Contributor

One proposed solution is to switch to chainsaw that can do resource templating (WIP PR #119).

See https://kyverno.io/blog/2024/02/15/kyverno-chainsaw-0.1.4-awesome-new-features/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants