use production images from registry.k8s.io in sample deployments

[TineoC]

Update sample deployments in the cluster/ directory to use production images from registry.k8s.io/slack-infra/.

This PR is part of the effort to migrate from staging GCR to production registry.k8s.io.
Promotion PR in k8s.io: kubernetes/k8s.io#9213

Note: slack-post-message is updated to the production registry path but still needs its SHA to be added to the promoter manifest in k8s.io if not already there.

Fixes #66

/sig contributor-experience
/area infra
/assign @BenTheElder @cpanato @jeefy @nikhita @spiffxp

[k8s-ci-robot]

@TineoC: The label(s) area/infra cannot be applied, because the repository doesn't have them.

Details

In response to this:

Update sample deployments in the cluster/ directory to use production images from registry.k8s.io/slack-infra/.

This PR is part of the effort to migrate from staging GCR to production registry.k8s.io.
Promotion PR in k8s.io: kubernetes/k8s.io#9213

Note: slack-post-message is updated to the production registry path but still needs its SHA to be added to the promoter manifest in k8s.io if not already there.

Fixes #66

/sig contributor-experience
/area infra
/assign @BenTheElder @cpanato @jeefy @nikhita @spiffxp

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.

[k8s-ci-robot]

@TineoC: GitHub didn't allow me to assign the following users: spiffxp.

Note that only kubernetes-sigs members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

Details

In response to this:

Update sample deployments in the cluster/ directory to use production images from registry.k8s.io/slack-infra/.

This PR is part of the effort to migrate from staging GCR to production registry.k8s.io.
Promotion PR in k8s.io: kubernetes/k8s.io#9213

Note: slack-post-message is updated to the production registry path but still needs its SHA to be added to the promoter manifest in k8s.io if not already there.

Fixes #66

/sig contributor-experience
/area infra
/assign @BenTheElder @cpanato @jeefy @nikhita @spiffxp

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.

[k8s-ci-robot]

Hi @TineoC. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: TineoC
Once this PR has been reviewed and has the lgtm label, please ask for approval from bentheelder. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[Prajyot-Parab]

/ok-to-test