-
Notifications
You must be signed in to change notification settings - Fork 15
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
[Manual] Deploy cluster components in development environment #3
Comments
Adding myself |
I am also up for this 👍🏽 |
I have a question here: can we involve the Falco guys to get Falco deployed manually in the cluster as a first step? We could just give them the kubeconfig and get started while we think more about the pipeline approach. What do you think? |
Could we start by asking the Falco team how they would recommend we do the install? Maybe we can install it rather than giving access to the cluster? |
Falco maintainers are in the process of creating a new repository (https://github.com/falcosecurity/cncf-green-review-testing) that will store everything needed from their side e.g. Falco deployment manifests, synthetic workload deployment manifests, benchmark tests, etc. However, Falco maintainers have less availability until early December. It would be better to go with a workaround until then! |
I'm guessing that they will use this Ansible config that they sent, at least in part: https://github.com/falcosecurity/kernel-testing/blob/main/ansible-playbooks/roles/bootstrap/tasks/main.yml We can always reach them through these issues if we need to ask them any questions: |
Synthetic workload has been installed we choose https://github.com/GoogleCloudPlatform/microservices-demo/tree/main/helm-chart#readme and we install it manually via helm, here there is a pull request for the 2-lines documentation on how to reproduce it |
I think we can close this issue, we have developed manually almost everything except from Falco |
Signed-off-by: Ross Fairbanks <[email protected]> Signed-off-by: Dipankar Das <[email protected]> * Provision cluster with OpenTofu Signed-off-by: Ross Fairbanks <[email protected]> * feat: Remove ansible and add worker node Signed-off-by: Ross Fairbanks <[email protected]> * fix: Add -enable to tofu init Signed-off-by: Ross Fairbanks <[email protected]> * fix: User data * first iteration adding k3s for k8s clusters bootstrap todo: need to test the script Signed-off-by: Dipankar Das <[email protected]> * comment to point out where is the kubeconfig Signed-off-by: Dipankar Das <[email protected]> * added var for k3s.version Signed-off-by: Dipankar Das <[email protected]> * removed deps for k3s agent token to use terraform/random NOTE: value will be added via env vars Signed-off-by: Dipankar Das <[email protected]> --------- Signed-off-by: Ross Fairbanks <[email protected]> Signed-off-by: Dipankar Das <[email protected]> Co-authored-by: Ross Fairbanks <[email protected]> Signed-off-by: Ross Fairbanks <[email protected]>
This is to create a dev environment for the Green Reviews WG.
Cluster Creation
Cluster Components
Manage cluster components:
Phase 1: Base-level cluster components (MVP)
Phase 2: Gather idle metrics for Falco
Note: Falco can be deployed by the WG contributors in this dev environment to ensure that it can run alongside Kepler without any issues. However, we aim to extract this so that CNCF Project maintainers are responsible for configuring the deployment of the CNCF Project itself.
Phase 3: Gather load-test metrics
Documentation
green-reviews-tooling
repository & the design docThe text was updated successfully, but these errors were encountered: