Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wording for variants of clusters for a cluster api provider #480

Closed
krisnova opened this issue Aug 15, 2018 · 24 comments
Closed

Wording for variants of clusters for a cluster api provider #480

krisnova opened this issue Aug 15, 2018 · 24 comments
Assignees

Comments

@krisnova
Copy link
Contributor

krisnova commented Aug 15, 2018

We have discovered that there are several use cases to have a variant of a kubernetes cluster for a specific environment (e.g. "provider").

The example I enjoy using (that I am sure everyone is sick of hearing) is public and private topology in kops.

Meaning that we drastically configure and build the network in AWS differently for the two types of clusters, so the deployment strategy is different for the two. But they are both valid AWS clusters.

Here is a fictional diagram that will demonstrate the layer we are discussing.

.
├── cluster-api-provider-aws
│   ├── private_topology
│   ├── public_topology
│   ├── with_asg
│   └── with_ec2
├── cluster-api-provider-gce
│   ├── gke
│   └── unmanaged
└── cluster-api-provider-vmware
    ├── bar
    ├── baz
    └── foo

Note: The names here are fictional and are in no way suggestions for real names. I chose these just to help clarify what the layer represents.

We decided that as a group, we need to have a word that represents this layer.

Below are suggested words that have been tossed around. If you like one of the words, please add a github emoji 👍 to the comment and cast a vote. Vote for as many as you like. Feel free to add your own if you can think of another word.

CC: @timothysc @roberthbailey

@krisnova
Copy link
Contributor Author

flavors

@krisnova
Copy link
Contributor Author

profiles

@krisnova
Copy link
Contributor Author

variants

@krisnova
Copy link
Contributor Author

implementations

@krisnova
Copy link
Contributor Author

styles

@krisnova
Copy link
Contributor Author

types

@davidjeddy
Copy link

Keeping with the nautical theme of K8:

Gulfs
Oceans
Seas
Whirlpool
Eddie
Fjord

@krisnova
Copy link
Contributor Author

@davidjeddy can you please separate your suggestions into single comments so folks can vote on them?

@ashish-amarnath
Copy link
Contributor

doing the work for @davidjeddy

@ashish-amarnath
Copy link
Contributor

Gulfs

@ashish-amarnath
Copy link
Contributor

Oceans

@ashish-amarnath
Copy link
Contributor

Seas

@ashish-amarnath
Copy link
Contributor

Whirlpool

@ashish-amarnath
Copy link
Contributor

Eddie

@ashish-amarnath
Copy link
Contributor

Fjord

@ndedic
Copy link

ndedic commented Aug 15, 2018

scenarios

(con: interchangeable with topologies?)

@davidewatson
Copy link
Contributor

davidewatson commented Aug 15, 2018

One reason I like the word variant is the existing English definition matches our intent closely:

variant := a form or version of something that differs in some respect from other forms of the same thing or from a standard.

Notice that the title of this issue even uses it...

Aside: I can't stop thinking of users when I hear the word profile... :)

@ashish-amarnath
Copy link
Contributor

+1 for the user-profile word association

@dtoebe
Copy link

dtoebe commented Aug 15, 2018

Mast

@dtoebe
Copy link

dtoebe commented Aug 15, 2018

@roberthbailey roberthbailey changed the title Wording for variants of clusters for a cloud Wording for variants of clusters for a cluster api provider Aug 16, 2018
@roberthbailey
Copy link
Contributor

/assign @kris-nova

@krisnova
Copy link
Contributor Author

krisnova commented Sep 5, 2018

Per cluster api call I am going to send an email to sig-arch and sig-cluster-lifecycle suggesting the word "variants" as our champion.

@davidewatson
Copy link
Contributor

@kris-nova: Should this be closed?

@roberthbailey
Copy link
Contributor

I think we can close this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants