-
Notifications
You must be signed in to change notification settings - Fork 43
Fix demo bundle deployment #776
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
Conversation
…to use demo values and simplified deployment for both demo and prod using the same script
…astore deployments and augmented it with setup_assets to configure the offline asset host
…test minikube kicbase images
…oy_charts to have uniform deployment, added more functions for calling_services and cert_manager
…s.example.yaml file, made it more precise based on yaml ops, add helm installation block
… to configure the whole setup
…c path with priviliged access
… access on ctr socket and allow waiting check
…ed in setup-offline-sources, couldn't use all targets which override ssh proxy vars ansible_ssh_common_args
…book tasks for each playbook
…to offer just the functions from external use
…etween task blocks, add wait log on long running tasks, add dynamic inventory and enable ssh proxy for them, import playbooks to break setup_assets.sh and offline_deploy_k8s into smaller tasks
…s and containers-system are taken care of by minikube
…system containers for minikube
…-sources and import its tasks directly in main vm-setup.yml to avoid setting up non-required archieves
…e file for all vars
…ble_ssh_private_key_file, UserKnownHostsFile while managing ssh connection, refractor verify_wire_ip and clean temp directory
… documentation to it (skip ci)
…or deploy_wiab (skip ci)
…replacing HOST_IP
|
# requirements | ||
# ubuntu 24.04 | ||
# amd64 architecture | ||
# Following ports to be available on it from stack-it guide |
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.
# Following ports to be available on it from stack-it guide | |
# The list of ports in the stack-it guide must be available. |
# amd64 architecture | ||
# Following ports to be available on it from stack-it guide | ||
|
||
# it should have all dns records configured as per DNS requirements |
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.
# it should have all dns records configured as per DNS requirements | |
#you should have all of the dns records of the given domain configured as per the DNS requirements at: |
# https://docs.wire.com/latest/how-to/install/includes/helm_dns-ingress-troubleshooting.inc.html | ||
target_domain: "example.com" | ||
|
||
# define this variable in case, deploying it in a private network |
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.
# define this variable in case, deploying it in a private network | |
# define this variable in case you are deploying wire on a private network, for local users only. |
|
||
# define this variable in case, deploying it in a private network | ||
# specify the external (Gateway) IP of the network where the deploy_node is present | ||
# by default, public ip address attached to the node will be used, if accessible over test_port in verify_wire_ip playbook |
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.
# by default, public ip address attached to the node will be used, if accessible over test_port in verify_wire_ip playbook | |
# by default, the public ip address attached directly to the target will be used, if it is accessible over test_port in verify_wire_ip playbook |
Change type
Basic information
Testing
Tracking
Knowledge Transfer
Motivation
Objective
Reason
Use case