-
Notifications
You must be signed in to change notification settings - Fork 44
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
[#1041] Minikube provider #1179
Conversation
2b75ed5
to
dac2572
Compare
dac2572
to
4b2c091
Compare
9f1265c
to
f5ebe6f
Compare
namespace: {{ .Values.global.namespace }} | ||
labels: | ||
app: ngrok-proxy | ||
spec: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A single ngrok tunnel that points to the ingress controller service instead of one per webhook
Co-authored-by: lucapette <ciao@lucapette.me>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work, tested and works perfectly 🎉
@@ -47,7 +47,7 @@ These settings are used to connect the **Airy Components** to your Kafka cluster | |||
- `endpoint` in `<HOSTNAME>:<PORT>` format | |||
- `dbName` name of the database in the PostgreSQL server | |||
- `username` these credentials will be passed to the **API Auth Component** | |||
- `password` and they will be used to create the Postgres if you are deploying with **Vagrant** | |||
- `password` and they will be used to create the Postgres database | |||
|
|||
### Components | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the ### Applying the configuration
section, we should also remove the --kube-config
flag, for applying the configuration.
|
||
```sh | ||
minikube -p airy-core destroy | ||
``` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we also write a note to delete the record from the /etc/hosts
file.
Even though it is not actually a problem, as when the new instance starts - it overwrites the existing one.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah I wouldn't bother with this for now. Since it does not break anything. Eventually we should have an airy destroy
command where we track this for each provider
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
airy config apply
now perfectly aligned 👍
434448c
to
91a93b6
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎉 🎉 🎉
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎉
resolves #1041
web-dev.sh
to run local setupsairy api endpoint
command to easily get the API endpoint