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

Remove ordering requirement in the spec.resources field #14

Open
lander2k2 opened this issue Jun 8, 2022 · 0 comments
Open

Remove ordering requirement in the spec.resources field #14

lander2k2 opened this issue Jun 8, 2022 · 0 comments

Comments

@lander2k2
Copy link
Contributor

Currently, the code generated from the following component config will not work. Because the ingress-ns.yaml namespace resource is not listed first, the creation of the contour-config will freeze and not progress. So we currently have a requirement to list namespaces first which is a bit of a booby trap.

name: contour-component
kind: ComponentWorkload
spec:
  api:
    group: ingress
    version: v1alpha1
    kind: Contour
    clusterScoped: true
  companionCliSubcmd:
    name: contour
    description: Manage contour component
  resources:
  - contour-config.yaml
  - ingress-ns.yaml
  - contour-deploy.yaml
  - contour-svc.yaml
  - envoy-ds.yaml
  dependencies:
  - ns-operator-component
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant