Observe k8s WG Demo Infrastructure

[kenfinnigan]

Please fill out the details below to file a request for access to the CNCF Community Infrastructure Lab. Please note that access is targeted to people working on specific open source projects; this is not designed just to get your feet wet. The most important answer is the URL of the project you'll be working with. If you're looking to learn Kubernetes and related technologies, please try out Katacoda.

First and Last Name

Ken Finnigan

Email

ken@kenfinnigan.me

Company/Organization

Workday

Job Title

Observability Architect / CNCF TAG Observability member

Project Title (i.e., a summary of what do you want to do, not what is the name of the open source project you're working with)

Observe k8s Demo

Briefly describe the project (i.e., what is the detail of what you're planning to do with these servers?)

The charter for the working group has full details of what is being planned, but the main focus is an interactive demo environment to learn about observability:

• Catalog of resources for learning about observability
• Rather than a scripted tutorial or guide, allow free experimentation.
• Demonstrate value of various solutions by (clonable, reproducible) examples. In other words “see it first, then easily replicate in your own env”
• Enable multiple views of the same underlying infra/workloads.

Is the code that you’re going to run 100% open source? If so, what is the URL or URLs where it is located? What is your association with that project?

https://github.com/observe-k8s

I participated in forming the Observe k8s Working Group, as part of CNCF TAG Observability, along with Matt Young (@halcyondude), Michael Hausenblas (@mhausenblas), and others.

What kind of machines and how many do you expect to use (see: https://metal.equinix.com/product/servers/)?

We would use the machines to create Kubernetes cluster(s) for hosting demo application(s) and the observability tooling.

We would expect to use: 1 x c3.medium.x86 as k8s control plane node 4 x s3.xlarge.x86 as k8s worker node

What operating system and networking are you planning to use?

Not finalized at present, but likely CentOS or Ubuntu.

Any other relevant details we should know about?

Matt Young (@halcyondude) and Michael Hausenblas (@mhausenblas) would also need access to the project.

[kenfinnigan]

/cc @halcyondude @mhausenblas

[halcyondude]

Questions for CNCF CIL folk...

• do we have dedicated interconnects (e.g. BGP) to route between VPC endpoints in azure/gcp/aws, or must we traverse public internet?
• Do we have a preferred k8s distro/cluster config for use in the CIL? Something via crossplane.io, or CAPI, or a pile of terraform, etc? We would prefer some degree of managed cluster (potentially) so that we don't burn opportunity cost running bespoke cluster(s).
• How do we manage CIL networking / dns currently? Is there already plumbed out external-dns configurations? for SSL certs do we have our own CA?
• How are Secrets managed today in CIL? Is there a vault instance (so we can use external-secrets controller, etc) already configured for use in the CIL?
• Does the CIL already have configured DDoS protection via CloudFlare, or some other provider, or should we assume it's DIY?

Thanks!

[jeefy]

• Not 100% sure. I know you can set up BGP routes, but I don't know enough to confidently answer. (cc @vielmetti )
• There is no preferred method here. Usually projects are coming in here with specific requests in mind, spin up machines, and go to town.
• Similar to above, it's however you want. Let's Encrypt is probably the norm here (via Cert-Manager)
• There's no central secrets manager for the CIL. These are all individual projects in Equinix under an umbrella account of the CNCF.
• Pretty much everything is DIY.

To put it another way, the CIL's whatever you make of it since you're given a piece to call your own. There are no pre-baked configs or settings within your project. We haven't had any requests for out-of-the-box configs or clusters, so this would be the first if that's what you'd eventually like to see.

cc'ing @caniszczyk for a +1

[caniszczyk]

+1

On Tue, Jun 28, 2022 at 10:24 AM Jeffrey Sica @.***> wrote:

• Not 100% sure. I know you can set up BGP routes, but I don't know enough to confidently answer. (cc @vielmetti https://github.com/vielmetti )
• There is no preferred method here. Usually projects are coming in here with specific requests in mind, spin up machines, and go to town.
• Similar to above, it's however you want. Let's Encrypt is probably the norm here (via Cert-Manager)
• There's no central secrets manager for the CIL. These are all individual projects in Equinix under an umbrella account of the CNCF.
• Pretty much everything is DIY.

To put it another way, the CIL's whatever you make of it since you're given a piece to call your own. There are no pre-baked configs or settings within your project. We haven't had any requests for out-of-the-box configs or clusters, so this would be the first if that's what you'd eventually like to see.

cc'ing @caniszczyk https://github.com/caniszczyk for a +1

— Reply to this email directly, view it on GitHub https://github.com/cncf/cluster/issues/212#issuecomment-1168868052, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAPSIPOO3SBOW2KXF5JFX3VRMKKXANCNFSM5XRZJXWQ . You are receiving this because you were mentioned.Message ID: @.***>

-- Cheers,

Chris Aniszczyk https://aniszczyk.org

[kenfinnigan]

What are the next steps for the process?

Is there any additional information required from us?

[kenfinnigan]

@jeefy what are the next steps for this process? Is there anything additional I need to provide or do? Thanks

[hh]

Invitation sent to ken@kenfinnigan.me to join the new observe-k8s infrastructure account.

[hh]

Created k8s-observe and invited these four via email:

• Ken Finnigan @kenfinnigan
• Matt Young @halcyondude
• michael.hausenblas
• henrik.rexed

[kenfinnigan]

Thanks all, will close as done

[kenfinnigan]

@hh could you add Sherwood Zern (@sherwoodzern) to the k8s-observe project? Thanks