kubectl cp
cat $src_filename | base64 -w 0 | kubectl exec -n $namespace $pod_name -i -- bash -c "base64 -d > $dest_filename"cat $src_filename | base64 -w 0 | kubectl exec -n $namespace $pod_name -i -- bash -c "base64 -d > $dest_filename"# --path is the dir with the app's kustomization.yaml.# --kustomization-file is the dir containing the FLUX kustomization object/file.
flux build kustomization my-app \ --path path/to/my-app \ --kustomization-file path/to/flux-kustomization.yaml \ --dry-run
# single lineflux build kustomization my-app --path path/to/my-app --kustomization-file path/to/flux-kustomization.yaml --dry-runTracing crossplane creation and errors can be done by tracing your custom resource. But you might have to trace errors in the underlying provider resources as well.
crossplane beta trace my-custom-resource-type my-custom-resource-namecrossplane beta trace bucketpolicy.s3.aws.upbound.io my-custom-resource-name# Need kubectl to find more verbose messages aboutkubectl get bucketpolicy.s3.aws.upbound.io my-custom-resource-name -oyamlStern isn’t that great to use to filter log messages in if you do not know jq/don’t have JSON format available but it is possible to escape characters when you use include.
stern -c istio-proxy -i '\"response_code\":200,' .stern -c istio-proxy -i '\"response_flags\":UH' .stern -c istio-proxy -i '\"response_flags\":\"-\"' .