-
Notifications
You must be signed in to change notification settings - Fork 166
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
Deploy Otomi on GKE cluster via GitHub Actions #1553
Comments
this command will remove the monitoring stack
|
We can set DNS if we have a NS record from the main domain to google DNS config Create Cloud DNS ZoneCreate a DNS zone which will contain the managed DNS records. If using your own domain that was registered with a third-party domain registrar, you should point your domain's name servers to the values under the gcloud dns managed-zones create $DNS_ZONE_NAME --dns-name $DOMAIN_NAME \
--description "Automatically managed zone by kubernetes.io/external-dns" Make a note of the nameservers that were assigned to your new zone. gcloud dns record-sets list \
--zone $DNS_ZONE_NAME --name $DOMAIN_NAME --type NS |
we want a static service account that we can use to create google resources and set DNS |
create cluster, note the
gcloud container clusters create $CLUSTER_NAME \
--enable-autoscaling \
--enable-network-policy \
--num-nodes 1 \
--min-nodes 1 \
--max-nodes 2 \
--machine-type $MACHINE_TYPE \
--logging NONE \
--monitoring NONE \
--region $COMPUTE_REGION |
--project=otomi-cloud |
Hey team! Please add your planning poker estimate with Zenhub @Ani1357 @dennisvankekem @ElderMatt @ferruhcihan @merll |
I see a lot of options here but let's start small. |
Thanks @dennisvankekem for sharing shell snippets! |
Additions
Changes
integration.yaml
is getting too convoluted.integration.yaml
and put them into their own files and include themThe text was updated successfully, but these errors were encountered: