search

kubernetes / examples

Kubernetes application example tutorials
Apache License 2.0
6.21k stars 4.54k forks source link

Broken image reference in guestbook example #519

Closed mocdaniel closed 1 month ago

mocdaniel commented 8 months ago

The image reference gcr.io/google-samples/gb-frontend:v4 in guestbook/frontend-deployment.yaml is invalid, the tag doesn't seem to exist (anymore).

After checking on gcr, it looks like there are no tags at all for gb-frontend, but only for the architecture-specific images, e.g. gb-frontend-amd64 or gb-frontend-arm.

k8s-ci-robot commented 8 months ago

@pranav-pandey0804: The label(s) sig/cluster, sig/lifecycle cannot be applied, because the repository doesn't have them.

In response to [this](https://github.com/kubernetes/examples/issues/519#issuecomment-2022596958): >/sig cluster lifecycle > 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.
pranav-pandey0804 commented 8 months ago

/sig cluster-lifecycle

neolit123 commented 6 months ago

i think this repository might contains some out-of-date examples, but they are not owned by SIG Cluster Lifecycle /remove-sig cluster-lifecycle

k8s-triage-robot commented 3 months ago

The Kubernetes project currently lacks enough 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 stale

oussaka commented 3 months ago

replace

      - name: php-redis
        image: gcr.io/google-samples/gb-frontend

by

      - name: php-redis
        image: us-docker.pkg.dev/google-samples/containers/gke/gb-frontend:v5
k8s-triage-robot commented 2 months 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 month 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 month ago

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

In response to [this](https://github.com/kubernetes/examples/issues/519#issuecomment-2409140861): >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-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.