You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The order in which the transformers are run is random. This means in some cases version conversion is not happening. This is especially a problem with --qa-skip where the default transformation option (first option) is selected for each service.
Steps To Reproduce
Create a src folder with an Ingress v1beta1 yaml file.
Do a move2kube transform -s src/
After the transformation is finished check the logs and the myproject output folder.
Expected behavior
The K8s version change transformer should run and change the Ingress yaml from v1beta1 to v1.
$ ls myproject/source/
ingress-1-versionchanged ingress-1-versionchanged-parameterized
Actual behavior
The K8s version change transformer only runs half the time randomly.
When it doesn't run, the output doesn't contain the version changed yamls.
Overview
The order in which the transformers are run is random. This means in some cases version conversion is not happening. This is especially a problem with
--qa-skipwhere the default transformation option (first option) is selected for each service.Steps To Reproduce
srcfolder with an Ingress v1beta1 yaml file.move2kube transform -s src/myprojectoutput folder.Expected behavior
The K8s version change transformer should run and change the Ingress yaml from v1beta1 to v1.
Actual behavior
The K8s version change transformer only runs half the time randomly.
When it doesn't run, the output doesn't contain the version changed yamls.
$ ls myproject/source/ ingress-1-parameterized $ cat myproject/source/ingress-1-parameterized/helm-chart/myproject/templates/ingress-0.yaml --- apiVersion: networking.k8s.io/v1beta1 kind: Ingress metadata: annotations: kubernetes.io/ingress.class: myingressclass-0 nginx.ingress.kubernetes.io/rewrite-target: /$1 name: ingress-0 spec: rules: - http: paths: - backend: serviceName: helloworld-svc-0 servicePort: 8080 path: /helloworld-0/(.*) ...Additional context
2 different plan files from the same input
and
The text was updated successfully, but these errors were encountered: