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

feat/local-setup #293

Merged
merged 7 commits into from
Feb 15, 2024
Merged

feat/local-setup #293

merged 7 commits into from
Feb 15, 2024

Conversation

roivaz
Copy link
Member

@roivaz roivaz commented Jan 29, 2024

This PR adds a new Makefile target and required assets and resources to create a 100% local saas environment.

  • Single command install all target that installs things in the correct order
  • All users/passwords are hard coded right now as this is a local-only env. Should never be deployed as-is behind a publicly accessible domain. To do so more work is still required to configure some things.
  • Autossl is deployed but does not work as it needs to be deployed in a publicly accessible domain, otherwise Let's Encrypt can never reach the endpoint to validate certificates.
  • config/local-setup/configuration.yaml can be used to modify each component image
  • https only configured for system using a self-signed CA
  • All endpoints are accessible locally using local IPs. These IPs are always the same. nip.io is used to generate the domain names of the components:
  • I encountered several problems when using mysql 8, so I just used mysql 5.7 for this first iteration.
  • System configuration is probably not 100% correct, but for our use case and testing needs is enough.
  • In order to use productized images, docker pull secrets are required. You need to add the file config/local-setup/secrets/pull-secrets.json with the tokens for the different registries used. Check the README for instructions (config/local-setup/README.md)
  • Just a couple of actual code changes in the PR:
    • I updated the description for several API fields, now that I know what they actually are.
    • Also updated the base reconciler config to be able to use metallb as the LoadBalancer provider in the cluster.

/kind feature
/priority important-soon
/assign

@3scale-robot 3scale-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Jan 29, 2024
@3scale-robot 3scale-robot added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next sprint. label Jan 29, 2024
@3scale-robot 3scale-robot added needs-size Indicates a PR or issue lacks a `size/foo` label and requires one. size/XL Requires about a week to complete the PR or the issue. and removed needs-size Indicates a PR or issue lacks a `size/foo` label and requires one. labels Jan 29, 2024
@roivaz roivaz force-pushed the feat/reproducible-dev-env branch from d750737 to 19e7053 Compare January 29, 2024 11:27
@roivaz roivaz force-pushed the feat/reproducible-dev-env branch from 19e7053 to 6c81dd4 Compare January 29, 2024 11:29
@roivaz roivaz force-pushed the feat/reproducible-dev-env branch 3 times, most recently from 351fe29 to 7b10ba6 Compare February 6, 2024 13:32
@roivaz roivaz force-pushed the feat/reproducible-dev-env branch from 7b10ba6 to bcfde24 Compare February 6, 2024 14:01
@3scale-robot 3scale-robot added the lgtm Indicates that a PR is ready to be merged. label Feb 15, 2024
@3scale-robot
Copy link
Contributor

LGTM label has been added.

Git tree hash: d5470900095ce1102d0db69f3712ba72a5c10902

@roivaz
Copy link
Member Author

roivaz commented Feb 15, 2024

/approve

@3scale-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: roivaz

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@3scale-robot 3scale-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 15, 2024
@3scale-robot 3scale-robot merged commit cd8a04b into main Feb 15, 2024
4 of 5 checks passed
@3scale-robot 3scale-robot deleted the feat/reproducible-dev-env branch February 15, 2024 14:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/feature Categorizes issue or PR as related to a new feature. lgtm Indicates that a PR is ready to be merged. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next sprint. size/XL Requires about a week to complete the PR or the issue.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants