eks-prow-build-cluster: separate canary manifests from prod

[pkprzekwas]

As we configure more services, differences between prod and canary configurations expands. In order to use Flux with different configs for prod and canary we need to create a dedicated set of manifests for canary. Previously we tries to use kustomize, but as explained in the PR, we decided that introduced complexity is to high. In new approach we simply duplicate manifests so that each cluster has a dedicated folder.

/area infra/aws
/assign @pkprzekwas
/cc @ameukam @dims @xmudrii

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[xmudrii]

/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[xmudrii]

Canary will be decommissioned after some testing is done, this is no longer relevant
/close

[k8s-ci-robot]

@xmudrii: Closing this issue.

In response to this:

Canary will be decommissioned after some testing is done, this is no longer relevant
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.