Moving Gcsweb to CNCF Infrastructure about k8s.io

[thockin]

DONE

[spiffxp]

/assign @bartsmykla

[bartsmykla]

@spiffxp, @thockin, @ixdy who should I poke to get some informations about cluster, where Gcsweb should be moved to (especially related to access)?

[dims]

/assign @thockin @ixdy

Tim, Jeff, can you please pull the existing manifests and let @bartsmykla take a peek?

[ixdy]

The existing manifests are in the gcsweb.k8s.io/ directory of this repo, currently running in the same Kubernetes cluster that we run the k8s.io redirector (and to which I recently deployed cert-manager). It runs in the gcsweb namespace, but I don't think that's encoded in the checked-in manifests (for whatever reason).

We don't really have any turnup scripts or anything, though I think you'd run into trouble creating the ingress right now due to cert-manager/cert-manager#1343. I guess if we update to cert-manager 0.7 that shouldn't be an issue, though.

I don't know where this would run in CNCF infrastructure.

[thockin]

We need to get the "real" cluster up in the next few weeks. Not much you can really do until then, sadly.

…

On Tue, Mar 12, 2019 at 2:40 PM Jeff Grafton ***@***.***> wrote: The existing manifests are in the gcsweb.k8s.io/ directory of this repo, currently running in the same Kubernetes cluster that we run the k8s.io redirector (and to which I recently deployed cert-manager). It runs in the gcsweb namespace, but I don't think that's encoded in the checked-in manifests (for whatever reason). We don't really have any turnup scripts or anything, though I think you'd run into trouble creating the ingress right now due to cert-manager/cert-manager#1343. I guess if we update to cert-manager 0.7 that shouldn't be an issue, though. I don't know where this would run in CNCF infrastructure. — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub, or mute the thread.

[dims]

needs a cluster

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[cblecker]

/remove-lifecycle stale