search

kubernetes / website

Kubernetes website and documentation repo:
https://kubernetes.io
Creative Commons Attribution 4.0 International
4.6k stars 14.49k forks source link

Update “Example: Deploying PHP Guestbook application with Redis” to use MultiArch images #35210

Closed camrossi closed 1 year ago

camrossi commented 2 years ago

I am testing the guestbook application on a ARM64 cluster and I noticed not all the images are multi arch.

This combination works for me: 

        image: "docker.io/redis:3.2.12"
        image: gcr.io/google-samples/gb-redisslave:v3
        image: gcr.io/google_samples/gb-frontend:v6

But I then had to modify the Services and Deployment to use the old non Bias-Free Language. It would be great if you could make the gb-redis-follower multi arch.

Also the gb-frontend should be v6 that is the multiarch version

k8s-ci-robot commented 2 years ago

@camrossi: This issue is currently awaiting triage.

SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
Shubham82 commented 2 years ago

page: https://kubernetes.io/docs/tutorials/stateless-application/guestbook/

sftim commented 2 years ago

To be honest, it might be easier to list AMD64 architecture as a pre-requisite.

sftim commented 2 years ago

/retitle Update “Example: Deploying PHP Guestbook application with Redis” to use MultiArch images

camrossi commented 2 years ago

Is not just Redis also front end was using the wrong tag and not working on ARM

On Sat, 23 Jul 2022 at 03:27, Tim Bannister @.***> wrote:

/retitle Update “Example: Deploying PHP Guestbook application with Redis” to use MultiArch images

— Reply to this email directly, view it on GitHub https://github.com/kubernetes/website/issues/35210#issuecomment-1192789636, or unsubscribe https://github.com/notifications/unsubscribe-auth/AD6E4PKB5LJYRBNVFFBFQR3VVLKXLANCNFSM54FVRSIA . You are receiving this because you were mentioned.Message ID: @.***>

camrossi commented 2 years ago

We could but all the images are already there, seems is a shame ?

On Sat, 23 Jul 2022 at 00:24, Tim Bannister @.***> wrote:

To be honest, it might be easier to list AMD64 architecture as a pre-requisite.

— Reply to this email directly, view it on GitHub https://github.com/kubernetes/website/issues/35210#issuecomment-1192628816, or unsubscribe https://github.com/notifications/unsubscribe-auth/AD6E4PLFPGW2RY55A6ZN5Y3VVKVJ3ANCNFSM54FVRSIA . You are receiving this because you were mentioned.Message ID: @.***>

k8s-triage-robot commented 1 year ago

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

This bot triages issues and PRs according to the following rules:

You can:

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

/lifecycle stale

k8s-triage-robot commented 1 year ago

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

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

You can:

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

/lifecycle rotten

k8s-triage-robot commented 1 year ago

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

This bot triages issues according to the following rules:

You can:

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

/close not-planned

k8s-ci-robot commented 1 year ago

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to [this](https://github.com/kubernetes/website/issues/35210#issuecomment-1463646464): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages 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: >- Reopen this issue with `/reopen` >- Mark this issue as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.