As of v1.3.4, LambdaStack requires you to change the following attributes in the either the minimal or full configuration YAML. Beginning in v2.0, you will have the option to pass in these parameters to override whatever is present in the yaml file. v2.0 is in active development
All options are defaults. Azure will automatically require you to login into the Azure portal before you can run LambdaStack for Azure unless you use the
service principaloption using the
Fullconfiguration. With the
Fullconfiguration you can specify your subscription name and service principal so that it can be machine-to-machine oriented not requiring any interaction
Attributes to change for the minimal configuration After you run `lambdastack init -p azure -n
prefix: staging- Staging is a default prefix. You can use whatever you like (e.g.,
production). This value can help group your AWS clusters in the same region for easier maintenance
name: operations- This attribute is under
specification.admin_user.nameand the default
key_path: lambdastack-operations- This is the default SSH key file(s) name. This is the name of your SSH public and private key pairs. For example, in this example, one file (private one) would be named
lambdastack-operations. The second file (public key) typically has a
.pubsuffix such as
use_public_ips: True- This is the default public IP value. Important, this attribute by default allows for AWS to build your clusters with a public IP interface. We also build a private (non-public) interface using private IPs for internal communication between the nodes. With this attribute set to
publicit simply allows you easy access to the cluster so you can SSH into it using the
nameattribute value from above. This is
NOT RECOMMENDEDfor sure not in production and not as a general rule. You should have a VPN or direct connect and route for the cluster
region: East US- This is the default region setting. This means that your cluster and storage will be created in Azure
East USregion. Important - If you want to change this value in any way, you should use the
full configurationand then change ALL references of region in the yaml file. If you do not then you may have services in regions you don't want and that may create problems for you
Now that you have made your changes to the
lambdastack apply -f build/<whatever you name your cluster>/<whatever you name your cluster>.yml. Now the building of a LambdaStack cluster will begin.
Apply option will generate a final
manifest.yml file that will be used for Terraform, Ansible and LambdaStack python code. The
manifest.yml will combine the values from below plus ALL yaml configuration files for each service.
--- kind: lambdastack-cluster title: "LambdaStack Cluster Config" provider: azure name: "default" build_path: "build/path" # This gets dynamically built specification: name: lambdastack prefix: staging # Can be anything you want that helps quickly identify the clusterprefix admin_user: name: operations # YOUR-ADMIN-USERNAME key_path: lambdastack-operations # YOUR-SSH-KEY-FILE-NAME path: "/shared/build/<name of cluster>/keys/ssh/lambdastack-operations" # Will get dynamically created cloud: k8s_as_cloud_service: False use_public_ips: True # When not using public IPs you have to provide connectivity via private IPs (VPN) region: East US default_os_image: default components: repository: count: 1 kubernetes_master: count: 1 kubernetes_node: count: 2 logging: count: 1 monitoring: count: 1 kafka: count: 2 postgresql: count: 1 load_balancer: count: 1 rabbitmq: count: 1
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.