RS-574: Create a development cluster for infra PRs

[gavin-stackrox]

Having a dev cluster ready to go when the image is built should be useful for most PRs. Ideally this automation would also do the render and install steps but I'm wary about copying configuration into CI so that may have to wait. Instead there is a whimsical comment added to the PR to suggest next steps 🚀

This PR also reorganizes infra CI by splitting the single workflow into separate PR and Release ones.

A follow up PR will deploy the dev infra to the development cluster: #711

[ghost]

A single node development cluster (infra-pr-710) was allocated in production infra for this PR.

🔌 You can connect to this cluster with:

gcloud container clusters get-credentials infra-pr-710 --zone us-central1-a --project srox-temp-dev-test

🚀 And then deploy your development infra-server with:

make render-local
make install-local

🛠️ And pull infractl from the deployed dev infra-server with:

nohup kubectl -n infra port-forward svc/infra-server-service 8443:8443 &
make pull-infractl-from-dev-server

🚲 You can then use the dev infra instance e.g.:

bin/infractl -k -e localhost:8443 whoami

⚠️Any clusters that you start using your dev infra instance should have a lifespan shorter
then the development cluster instance. Otherwise they will not be destroyed when the dev infra instance
ceases to exist when the development cluster is deleted.⚠️

[parametalol]

Please see https://github.com/stackrox/test-gh-actions/pull/47 and https://github.com/stackrox/actions

[tommartensen]

Just a comment: If PRs deploy to dev clusters, what is dev.infra.rox.systems?
Seems to me like we are starting to overload the term "dev cluster" :)

[gavin-stackrox]

Just a comment: If PRs deploy to dev clusters, what is dev.infra.rox.systems? Seems to me like we are starting to overload the term "dev cluster" :)

It is a v. valid point. I think we are continuing to overload dev. dev.infra.rox.systems should be migrated to staging.infra.rox.systems. It was a development cluster when the original infra creator was the sole dev but now its staging for validating deployment prior to production.

[gavin-stackrox]

Having a dev cluster ready to go when the image is built should be useful for most PRs. Ideally this automation would also do the render and install steps but I'm wary about copying configuration into CI so that may have to wait. Instead there is a whimsical comment added to the PR to suggest next steps 🚀

This PR also reorganizes infra CI by splitting the single workflow into separate PR and Release ones.

A follow up PR will deploy the dev infra to the development cluster: #711

[ghost]

A single node development cluster (infra-pr-710) was allocated in production infra for this PR.

🔌 You can connect to this cluster with:

gcloud container clusters get-credentials infra-pr-710 --zone us-central1-a --project srox-temp-dev-test

🚀 And then deploy your development infra-server with:

make render-local
make install-local

🛠️ And pull infractl from the deployed dev infra-server with:

nohup kubectl -n infra port-forward svc/infra-server-service 8443:8443 &
make pull-infractl-from-dev-server

🚲 You can then use the dev infra instance e.g.:

bin/infractl -k -e localhost:8443 whoami

⚠️Any clusters that you start using your dev infra instance should have a lifespan shorter
then the development cluster instance. Otherwise they will not be destroyed when the dev infra instance
ceases to exist when the development cluster is deleted.⚠️

[parametalol]

Please see https://github.com/stackrox/test-gh-actions/pull/47 and https://github.com/stackrox/actions

[tommartensen]

Just a comment: If PRs deploy to dev clusters, what is dev.infra.rox.systems?
Seems to me like we are starting to overload the term "dev cluster" :)

[gavin-stackrox]

Just a comment: If PRs deploy to dev clusters, what is dev.infra.rox.systems? Seems to me like we are starting to overload the term "dev cluster" :)

It is a v. valid point. I think we are continuing to overload dev. dev.infra.rox.systems should be migrated to staging.infra.rox.systems. It was a development cluster when the original infra creator was the sole dev but now its staging for validating deployment prior to production.

[gavin-stackrox]

Having a dev cluster ready to go when the image is built should be useful for most PRs. Ideally this automation would also do the render and install steps but I'm wary about copying configuration into CI so that may have to wait. Instead there is a whimsical comment added to the PR to suggest next steps 🚀

This PR also reorganizes infra CI by splitting the single workflow into separate PR and Release ones.

A follow up PR will deploy the dev infra to the development cluster: #711

[ghost]

A single node development cluster (infra-pr-710) was allocated in production infra for this PR.

🔌 You can connect to this cluster with:

gcloud container clusters get-credentials infra-pr-710 --zone us-central1-a --project srox-temp-dev-test

🚀 And then deploy your development infra-server with:

make render-local
make install-local

🛠️ And pull infractl from the deployed dev infra-server with:

nohup kubectl -n infra port-forward svc/infra-server-service 8443:8443 &
make pull-infractl-from-dev-server

🚲 You can then use the dev infra instance e.g.:

bin/infractl -k -e localhost:8443 whoami

⚠️Any clusters that you start using your dev infra instance should have a lifespan shorter
then the development cluster instance. Otherwise they will not be destroyed when the dev infra instance
ceases to exist when the development cluster is deleted.⚠️

[parametalol]

Please see https://github.com/stackrox/test-gh-actions/pull/47 and https://github.com/stackrox/actions

[tommartensen]

Just a comment: If PRs deploy to dev clusters, what is dev.infra.rox.systems?
Seems to me like we are starting to overload the term "dev cluster" :)

[gavin-stackrox]

Just a comment: If PRs deploy to dev clusters, what is dev.infra.rox.systems? Seems to me like we are starting to overload the term "dev cluster" :)

It is a v. valid point. I think we are continuing to overload dev. dev.infra.rox.systems should be migrated to staging.infra.rox.systems. It was a development cluster when the original infra creator was the sole dev but now its staging for validating deployment prior to production.

[gavin-stackrox]

Having a dev cluster ready to go when the image is built should be useful for most PRs. Ideally this automation would also do the render and install steps but I'm wary about copying configuration into CI so that may have to wait. Instead there is a whimsical comment added to the PR to suggest next steps 🚀

This PR also reorganizes infra CI by splitting the single workflow into separate PR and Release ones.

A follow up PR will deploy the dev infra to the development cluster: #711

[ghost]

A single node development cluster (infra-pr-710) was allocated in production infra for this PR.

🔌 You can connect to this cluster with:

gcloud container clusters get-credentials infra-pr-710 --zone us-central1-a --project srox-temp-dev-test

🚀 And then deploy your development infra-server with:

make render-local
make install-local

🛠️ And pull infractl from the deployed dev infra-server with:

nohup kubectl -n infra port-forward svc/infra-server-service 8443:8443 &
make pull-infractl-from-dev-server

🚲 You can then use the dev infra instance e.g.:

bin/infractl -k -e localhost:8443 whoami

⚠️Any clusters that you start using your dev infra instance should have a lifespan shorter
then the development cluster instance. Otherwise they will not be destroyed when the dev infra instance
ceases to exist when the development cluster is deleted.⚠️

[parametalol]

Please see https://github.com/stackrox/test-gh-actions/pull/47 and https://github.com/stackrox/actions

[tommartensen]

Just a comment: If PRs deploy to dev clusters, what is dev.infra.rox.systems?
Seems to me like we are starting to overload the term "dev cluster" :)

[gavin-stackrox]

Just a comment: If PRs deploy to dev clusters, what is dev.infra.rox.systems? Seems to me like we are starting to overload the term "dev cluster" :)

It is a v. valid point. I think we are continuing to overload dev. dev.infra.rox.systems should be migrated to staging.infra.rox.systems. It was a development cluster when the original infra creator was the sole dev but now its staging for validating deployment prior to production.

[gavin-stackrox]

Having a dev cluster ready to go when the image is built should be useful for most PRs. Ideally this automation would also do the render and install steps but I'm wary about copying configuration into CI so that may have to wait. Instead there is a whimsical comment added to the PR to suggest next steps 🚀

This PR also reorganizes infra CI by splitting the single workflow into separate PR and Release ones.

A follow up PR will deploy the dev infra to the development cluster: #711

[ghost]

A single node development cluster (infra-pr-710) was allocated in production infra for this PR.

🔌 You can connect to this cluster with:

gcloud container clusters get-credentials infra-pr-710 --zone us-central1-a --project srox-temp-dev-test

🚀 And then deploy your development infra-server with:

make render-local
make install-local

🛠️ And pull infractl from the deployed dev infra-server with:

nohup kubectl -n infra port-forward svc/infra-server-service 8443:8443 &
make pull-infractl-from-dev-server

🚲 You can then use the dev infra instance e.g.:

bin/infractl -k -e localhost:8443 whoami

⚠️Any clusters that you start using your dev infra instance should have a lifespan shorter
then the development cluster instance. Otherwise they will not be destroyed when the dev infra instance
ceases to exist when the development cluster is deleted.⚠️

[parametalol]

Please see https://github.com/stackrox/test-gh-actions/pull/47 and https://github.com/stackrox/actions

[tommartensen]

Just a comment: If PRs deploy to dev clusters, what is dev.infra.rox.systems?
Seems to me like we are starting to overload the term "dev cluster" :)

[gavin-stackrox]

Just a comment: If PRs deploy to dev clusters, what is dev.infra.rox.systems? Seems to me like we are starting to overload the term "dev cluster" :)

It is a v. valid point. I think we are continuing to overload dev. dev.infra.rox.systems should be migrated to staging.infra.rox.systems. It was a development cluster when the original infra creator was the sole dev but now its staging for validating deployment prior to production.

[gavin-stackrox]

Having a dev cluster ready to go when the image is built should be useful for most PRs. Ideally this automation would also do the render and install steps but I'm wary about copying configuration into CI so that may have to wait. Instead there is a whimsical comment added to the PR to suggest next steps 🚀

This PR also reorganizes infra CI by splitting the single workflow into separate PR and Release ones.

A follow up PR will deploy the dev infra to the development cluster: #711

[ghost]

A single node development cluster (infra-pr-710) was allocated in production infra for this PR.

🔌 You can connect to this cluster with:

gcloud container clusters get-credentials infra-pr-710 --zone us-central1-a --project srox-temp-dev-test

🚀 And then deploy your development infra-server with:

make render-local
make install-local

🛠️ And pull infractl from the deployed dev infra-server with:

nohup kubectl -n infra port-forward svc/infra-server-service 8443:8443 &
make pull-infractl-from-dev-server

🚲 You can then use the dev infra instance e.g.:

bin/infractl -k -e localhost:8443 whoami

⚠️Any clusters that you start using your dev infra instance should have a lifespan shorter
then the development cluster instance. Otherwise they will not be destroyed when the dev infra instance
ceases to exist when the development cluster is deleted.⚠️

[parametalol]

Please see https://github.com/stackrox/test-gh-actions/pull/47 and https://github.com/stackrox/actions

[tommartensen]

Just a comment: If PRs deploy to dev clusters, what is dev.infra.rox.systems?
Seems to me like we are starting to overload the term "dev cluster" :)

[gavin-stackrox]

Just a comment: If PRs deploy to dev clusters, what is dev.infra.rox.systems? Seems to me like we are starting to overload the term "dev cluster" :)

It is a v. valid point. I think we are continuing to overload dev. dev.infra.rox.systems should be migrated to staging.infra.rox.systems. It was a development cluster when the original infra creator was the sole dev but now its staging for validating deployment prior to production.

[gavin-stackrox]

Having a dev cluster ready to go when the image is built should be useful for most PRs. Ideally this automation would also do the render and install steps but I'm wary about copying configuration into CI so that may have to wait. Instead there is a whimsical comment added to the PR to suggest next steps 🚀

This PR also reorganizes infra CI by splitting the single workflow into separate PR and Release ones.

A follow up PR will deploy the dev infra to the development cluster: #711

[ghost]

A single node development cluster (infra-pr-710) was allocated in production infra for this PR.

🔌 You can connect to this cluster with:

gcloud container clusters get-credentials infra-pr-710 --zone us-central1-a --project srox-temp-dev-test

🚀 And then deploy your development infra-server with:

make render-local
make install-local

🛠️ And pull infractl from the deployed dev infra-server with:

nohup kubectl -n infra port-forward svc/infra-server-service 8443:8443 &
make pull-infractl-from-dev-server

🚲 You can then use the dev infra instance e.g.:

bin/infractl -k -e localhost:8443 whoami

⚠️Any clusters that you start using your dev infra instance should have a lifespan shorter
then the development cluster instance. Otherwise they will not be destroyed when the dev infra instance
ceases to exist when the development cluster is deleted.⚠️

[parametalol]

Please see https://github.com/stackrox/test-gh-actions/pull/47 and https://github.com/stackrox/actions

[tommartensen]

Just a comment: If PRs deploy to dev clusters, what is dev.infra.rox.systems?
Seems to me like we are starting to overload the term "dev cluster" :)

[gavin-stackrox]

Just a comment: If PRs deploy to dev clusters, what is dev.infra.rox.systems? Seems to me like we are starting to overload the term "dev cluster" :)

It is a v. valid point. I think we are continuing to overload dev. dev.infra.rox.systems should be migrated to staging.infra.rox.systems. It was a development cluster when the original infra creator was the sole dev but now its staging for validating deployment prior to production.

[gavin-stackrox]

Having a dev cluster ready to go when the image is built should be useful for most PRs. Ideally this automation would also do the render and install steps but I'm wary about copying configuration into CI so that may have to wait. Instead there is a whimsical comment added to the PR to suggest next steps 🚀

This PR also reorganizes infra CI by splitting the single workflow into separate PR and Release ones.

A follow up PR will deploy the dev infra to the development cluster: #711

[ghost]

A single node development cluster (infra-pr-710) was allocated in production infra for this PR.

🔌 You can connect to this cluster with:

gcloud container clusters get-credentials infra-pr-710 --zone us-central1-a --project srox-temp-dev-test

🚀 And then deploy your development infra-server with:

make render-local
make install-local

🛠️ And pull infractl from the deployed dev infra-server with:

nohup kubectl -n infra port-forward svc/infra-server-service 8443:8443 &
make pull-infractl-from-dev-server

🚲 You can then use the dev infra instance e.g.:

bin/infractl -k -e localhost:8443 whoami

⚠️Any clusters that you start using your dev infra instance should have a lifespan shorter
then the development cluster instance. Otherwise they will not be destroyed when the dev infra instance
ceases to exist when the development cluster is deleted.⚠️

[parametalol]

Please see https://github.com/stackrox/test-gh-actions/pull/47 and https://github.com/stackrox/actions

[tommartensen]

Just a comment: If PRs deploy to dev clusters, what is dev.infra.rox.systems?
Seems to me like we are starting to overload the term "dev cluster" :)

[gavin-stackrox]

Just a comment: If PRs deploy to dev clusters, what is dev.infra.rox.systems? Seems to me like we are starting to overload the term "dev cluster" :)

It is a v. valid point. I think we are continuing to overload dev. dev.infra.rox.systems should be migrated to staging.infra.rox.systems. It was a development cluster when the original infra creator was the sole dev but now its staging for validating deployment prior to production.