RetroSearch Browse

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://developer.hashicorp.com/terraform/enterprise/deploy/podman below:

Deploy Terraform Enterprise to Podman | Terraform

This topic describes how to install and run Terraform Enterprise on Podman. These installation steps set up a rootful Podman installation with a non-root user so that the Podman service runs as root while processes within the Terraform Enterprise container run as non-root.

Complete the following steps to install Terraform Enterprise:

Complete the prerequisites.
Set up installation folders and files.
Download and install image.
Apply the deployment configuration.

Complete the following tasks before attempting to install Terraform Enterprise.

Prepare the deployment environment

Set up a host instance and provide a DNS hostname for Terraform Enterprise and the associated TLS certificate. Additionally, you must configure your network so that your host can receive and send traffic. Refer to Prepare the host environment for details about preparing the host environment.

Deploy storage systems for active and external mode

If you intend to operate Terraform Enterprise in active or external mode, deploy the database and other storage devices so that Terraform can connect to them when the application starts. Refer to Data storage settings overview for additional information.

Create the deployment configuration

Create a deployment configuration file and specify settings for the operational mode, license, TLS certificates, and network configuration. Add any additional configurations necessary for your environment. Refer to Configuration file overview for additional information.

Connect to the host instance.
Create a dedicated directory for the Terraform Enterprise installation files
Navigate to the installation directory.
Create a certs directory.
Place your TLS certificate (cert.pem), TLS private key (key.pem), and CA certificates bundle (bundle.pem) inside inside thecerts directory. If you do not have a CA certificates bundle, place your TLS certificate (cert.pem) inside bundle.pem instead.
Place your deployment configuration file into the Terraform Enterprise installation directory. Refer to Example deployment configurations for pre-formatted configurations that you can copy and modify. Refer to the configuration reference for information about all deployment configuration settings.

Log in to the Terraform Enterprise container image registry, using terraform as the username, and your Hashicorp Terraform Enterprise license as the password:
```
# echo "<HASHICORP_LICENSE>" |  podman login --username terraform images.releases.hashicorp.com --password-stdin
```

Pull the Terraform Enterprise image from the registry.

# podman pull images.releases.hashicorp.com/hashicorp/terraform-enterprise:<vYYYYMM-#>

Refer to Deployment configuration reference for a list of all the configuration options.

Create a Terraform Enterprise pod by running the following command:
```
# podman kube play <path_to_YAML_file>
```
In a separate terminal session, you can monitor the logs by running the following command:
```
# podman logs -f <container_name>
```
Monitor the health of the application until it starts reporting healthy with the following command:
```
# podman exec <container_name> tfe-health-check-status
```

Post installation tasks actions

Complete the following tasks after the initial installation.

Review startup checks

When you start Terraform Enterprise, several startup checks also run to prevent errors related to invalid configurations or certificates, as well as other issues that could prevent the application from running successfully or safely. Refer to the startup checks reference for additional information.

Create the initial admin user

Provision your first administrative user and start using Terraform Enterprise.

Service management

To learn more about managing the lifecycle of Podman pods, refer to the Podman docs for more information about pods. We have included possible options for managing a pod's lifecycle on a Red Hat Enterprise Linux (RHEL) host for convenience.

Manage Podman service

Complete the following steps to create a systemd service that automatically starts your pod and its containers. We recommend using Quadlet, which is an opinionated tool for running Podman containers, to deploy systemd. Quadlet generates a systemd service that manages the Terraform Enterprise pod and all containers, including the internal infrastructure container.

Ensure the Terraform Enterprise pod is not running.
Navigate to /etc/containers/systemd/. Define the service files in this directory.
Create a Quadlet unit file for the Terraform Enterprise pod and container at /etc/containers/systemd/terraform-enterprise.kube:
```
  [Install]
  WantedBy=default.target
  [Service]
  Restart=always
  [Kube]
  Yaml=tfe.yaml
```
Copy your Kubernetes YAML file to /etc/containers/systemd/tfe.yaml:
```
# cp <path_to_YAML_file> /etc/containers/systemd/tfe.yaml
```

Reload the systemd daemon and enable the service:

# systemctl daemon-reload
# systemctl start terraform-enterprise.service

Check the status of your service:

# systemctl status terraform-enterprise.service

  ● terraform-enterprise.service
    Loaded: loaded (/etc/containers/systemd/terraform-enterprise.kube; generated)
    Active: active (running) since Sun 2024-02-25 21:15:55 UTC; 15min ago
  Main PID: 35893 (conmon)
      Tasks: 4 (limit: 404901)
    Memory: 5.2M
    CGroup: /system.slice/terraform-enterprise.service
            ├─35893 /usr/bin/conmon --api-version 1 -c 74f1271d9a481711950c62b509f126c3fdf8678a9d552c5ccc692eb6ed5cf4d1 -u 74f1271d9a481711950c62b509f126c3fdf8678a9d552c5ccc692eb6ed5cf4d1 ->
            ├─36028 /usr/sbin/dnsmasq -u root --conf-file=/run/containers/cni/dnsname/podman-default-kube-network/dnsmasq.conf
            ├─36030 /usr/bin/conmon --api-version 1 -c 973d3ff4f7ada5880a9947be4d90b3d556c7ce841037de34c7eaa07c044a3ec0 -u 973d3ff4f7ada5880a9947be4d90b3d556c7ce841037de34c7eaa07c044a3ec0 ->
            └─36083 /usr/bin/conmon --api-version 1 -c 435ea68e87dbef3c0965ffdfb9fe1fc36c5500a63eb00dc0fe2499aaa560a563 -u 435ea68e87dbef3c0965ffdfb9fe1fc36c5500a63eb00dc0fe2499aaa560a563 ->

You can copy one of the following example configurations and modify the values to per your environment. Refer to Configuration Reference for a list of all configuration options.

Example disk mode configuration

The following Kubernetes YAML deploys Terraform Enterprise in disk mode. In this mode, Terraform Enterprise runs as a pod composed of a Terraform Enterprise container.

---
apiVersion: "v1"
kind: "Pod"
metadata:
  labels:
    app: "terraform-enterprise"
  name: "terraform-enterprise"
spec:
  restartPolicy: "Never"
  containers:
  - env:
    - name: "TFE_OPERATIONAL_MODE"
      value: "disk"
    - name: "TFE_LICENSE"
      value: "<HashiCorp license>"
    - name: "TFE_HOSTNAME"
      value: "<Hostname>"
    - name: "TFE_HTTP_PORT"
      value: "8080"
    - name: "TFE_HTTPS_PORT"
      value: "8443"
    - name: "TFE_TLS_CERT_FILE"
      value: "/etc/ssl/private/terraform-enterprise/cert.pem"
    - name: "TFE_TLS_KEY_FILE"
      value: "/etc/ssl/private/terraform-enterprise/key.pem"
    - name: "TFE_TLS_CA_BUNDLE_FILE"
      value: "/etc/ssl/private/terraform-enterprise/bundle.pem"
    - name: "TFE_DISK_CACHE_VOLUME_NAME"
      value: "terraform-enterprise_terraform-enterprise-cache"
    - name: "TFE_ENCRYPTION_PASSWORD"
      value: '<Encryption password>'
    image: "images.releases.hashicorp.com/hashicorp/terraform-enterprise:<vYYYYMM-#>"
    name: "terraform-enterprise"
    ports:
    - containerPort: 8080
      hostPort: 80
    - containerPort: 8443
      hostPort: 443
    - containerPort: 9090
      hostPort: 9090
    securityContext:
      capabilities:
        add:
        - "CAP_IPC_LOCK"
      readOnlyRootFilesystem: true
      seLinuxOptions:
        type: "spc_t"
    volumeMounts:
    - mountPath: "/etc/ssl/private/terraform-enterprise"
      name: "certs"
    - mountPath: "/var/log/terraform-enterprise"
      name: "log"
    - mountPath: "/run"
      name: "run"
    - mountPath: "/tmp"
      name: "tmp"
    - mountPath: "/var/lib/terraform-enterprise"
      name: "data"
    - mountPath: "/run/docker.sock"
      name: "docker-sock"
    - mountPath: "/var/cache/tfe-task-worker/terraform"
      name: "terraform-enterprise_terraform-enterprise-cache-pvc"
  volumes:
  - hostPath:
      path: "<path_to_certs_on_host>"
      type: "Directory"
    name: "certs"
  - emptyDir:
      medium: "Memory"
    name: "log"
  - emptyDir:
      medium: "Memory"
    name: "run"
  - emptyDir:
      medium: "Memory"
    name: "tmp"
  - hostPath:
      path: "<mounted_disk_path_on_host>"
      type: "Directory"
    name: "data"
  - hostPath:
      path: "/run/podman/podman.sock"
      type: "File"
    name: "docker-sock"
  - name: "terraform-enterprise_terraform-enterprise-cache-pvc"
    persistentVolumeClaim:
      claimName: "terraform-enterprise_terraform-enterprise-cache"

Example external mode configuration

The following Kubernetes YAML configuration deploys Terraform Enterprise in external mode. In this mode, Terraform Enterprise runs as a pod composed of a Terraform Enterprise container.

---
apiVersion: "v1"
kind: "Pod"
metadata:
  labels:
    app: "terraform-enterprise"
  name: "terraform-enterprise"
spec:
  restartPolicy: "Never"
  containers:
  - env:
    - name: "TFE_LICENSE"
      value: "<HashiCorp license>"
    - name: "TFE_HOSTNAME"
      value: "<TFE hostname>"
    - name: "TFE_OPERATIONAL_MODE"
      value: "external"
    - name: "TFE_HTTP_PORT"
      value: "8080"
    - name: "TFE_HTTPS_PORT"
      value: "8443"
    - name: "TFE_ENCRYPTION_PASSWORD"
      value: '<Encryption password>'
    - name: "TFE_DISK_CACHE_VOLUME_NAME"
      value: "terraform-enterprise_terraform-enterprise-cache"
    - name: "TFE_TLS_CA_BUNDLE_FILE"
      value: "/etc/ssl/private/terraform-enterprise/bundle.pem"
    - name: "TFE_TLS_CERT_FILE"
      value: "/etc/ssl/private/terraform-enterprise/cert.pem"
    - name: "TFE_TLS_KEY_FILE"
      value: "/etc/ssl/private/terraform-enterprise/key.pem"


    # Database settings. See the configuration reference for more settings.
    - name: "TFE_DATABASE_HOST"
      value: "<Database hostname and port e.g. postgres:5432>"
    - name: "TFE_DATABASE_NAME"
      value: "<Database name e.g. hashicorp>"
    - name: "TFE_DATABASE_PARAMETERS"
      value: "<Database parameters e.g. sslmode=disable>"
    - name: 'TFE_DATABASE_PASSWORD'
      value: "<Database password e.g. postgres>"
    - name: "TFE_DATABASE_USER"
      value: "<Database user e.g. postgres>"

    # Object storage settings. See the configuration reference for more settings.
    - name: "TFE_OBJECT_STORAGE_TYPE"
      value: "s3"
    - name: "TFE_OBJECT_STORAGE_S3_ACCESS_KEY_ID"
      value: "<AWS Access Key ID>"
    - name: "TFE_OBJECT_STORAGE_S3_SECRET_ACCESS_KEY"
      value: '<AWS Secret Access Key>'
    - name: "TFE_OBJECT_STORAGE_S3_BUCKET"
      value: "<Bucket name>"
    - name: "TFE_OBJECT_STORAGE_S3_REGION"
      value: "<AWS region>"

    image: "images.releases.hashicorp.com/hashicorp/terraform-enterprise:<vYYYYMM-#>"
    name: "terraform-enterprise"
    ports:
    - containerPort: 8080
      hostPort: 80
    - containerPort: 8443
      hostPort: 443
    - containerPort: 9090
      hostPort: 9090
    securityContext:
      capabilities:
        add:
        - "CAP_IPC_LOCK"
      readOnlyRootFilesystem: true
      seLinuxOptions:
        type: "spc_t"
    volumeMounts:
    - mountPath: "/etc/ssl/private/terraform-enterprise"
      name: "certs"
    - mountPath: "/var/log/terraform-enterprise"
      name: "log"
    - mountPath: "/run"
      name: "run"
    - mountPath: "/tmp"
      name: "tmp"
    - mountPath: "/run/docker.sock"
      name: "docker-sock"
    - mountPath: "/var/cache/tfe-task-worker/terraform"
      name: "terraform-enterprise_terraform-enterprise-cache-pvc"
  volumes:
  - hostPath:
      path: "<path_to_certs_on_host>"
      type: "Directory"
    name: "certs"
  - emptyDir:
      medium: "Memory"
    name: "log"
  - emptyDir:
      medium: "Memory"
    name: "run"
  - emptyDir:
      medium: "Memory"
    name: "tmp"
  - hostPath:
      path: "/run/podman/podman.sock"
      type: "File"
    name: "docker-sock"
  - name: "terraform-enterprise_terraform-enterprise-cache-pvc"
    persistentVolumeClaim:
      claimName: "terraform-enterprise_terraform-enterprise-cache"

Example active-active mode configuration

The following Kubernetes YAML configuration deploys Terraform Enterprise in active-active mode. In this mode, each node runs a Podman pod composed of a Terraform Enterprise container.

---
apiVersion: "v1"
kind: "Pod"
metadata:
  labels:
    app: "terraform-enterprise"
  name: "terraform-enterprise"
spec:
  containers:
  - env:
    - name: "TFE_LICENSE"
      value: "<HashiCorp license>"
    - name: "TFE_HOSTNAME"
      value: "<TFE hostname>"
    - name: "TFE_HTTP_PORT"
      value: "8080"
    - name: "TFE_HTTPS_PORT"
      value: "8443"
    - name: "TFE_OPERATIONAL_MODE"
      value: "active-active"
    - name: "TFE_ENCRYPTION_PASSWORD"
      value: '<Encryption password>'
    - name: "TFE_DISK_CACHE_VOLUME_NAME"
      value: "terraform-enterprise_terraform-enterprise-cache"
    - name: "TFE_TLS_CA_BUNDLE_FILE"
      value: "/etc/ssl/private/terraform-enterprise/bundle.pem"
    - name: "TFE_TLS_CERT_FILE"
      value: "/etc/ssl/private/terraform-enterprise/cert.pem"
    - name: "TFE_TLS_KEY_FILE"
      value: "/etc/ssl/private/terraform-enterprise/key.pem"

    # Database settings. See the configuration reference for more settings.
    - name: "TFE_DATABASE_HOST"
      value: "<Database hostname and port e.g. postgres:5432>"
    - name: "TFE_DATABASE_NAME"
      value: "<Database name e.g. hashicorp>"
    - name: "TFE_DATABASE_PARAMETERS"
      value: "<Database parameters e.g. sslmode=disable>"
    - name: "TFE_DATABASE_PASSWORD"
      value: '<Database password>'
    - name: "TFE_DATABASE_USER"
      value: "<Database user e.g. postgres>"

    # Object storage settings. See the configuration reference for more settings.
    - name: "TFE_OBJECT_STORAGE_TYPE"
      value: "s3"
    - name: "TFE_OBJECT_STORAGE_S3_ACCESS_KEY_ID"
      value: "<AWS Access Key ID>"
    - name: "TFE_OBJECT_STORAGE_S3_SECRET_ACCESS_KEY"
      value: '<AWS Secret Access Key>'
    - name: "TFE_OBJECT_STORAGE_S3_BUCKET"
      value: "<Bucket name>"
    - name: "TFE_OBJECT_STORAGE_S3_REGION"
      value: "<AWS region>"

     # Redis settings. See the configuration reference for more settings.
    - name: "TFE_REDIS_HOST"
      value: "<Redis hostname and port>"
    - name: "TFE_REDIS_PASSWORD"
      value: '<Redis password>'
    - name: "TFE_REDIS_USER"
      value: "<Redis username>"
    - name: "TFE_REDIS_USE_AUTH"
      value: "<To use customized credential to authenticate? e.g. false>"
    - name: "TFE_REDIS_USE_TLS"
      value: "<To use tls? e.g. false>"
    - name: "TFE_REDIS_USE_MTLS"
      value: "<To use mtls with Redis standalone or Sentinel? eg. "false">
    - name: "TFE_REDIS_CLIENT_CERT_PATH"
      value: "<Path to the client certificate file to be used for mTLS authentication with Redis server>
    - name: "TFE_REDIS_CA_CERT_PATH"
      value: "<Path to the Certificate Authority file user to validate the certificate>"
    - name: "TFE_REDIS_CLIENT_KEY_PATH"
      value: "<Path to the private key file corresponding to the client certificate>"
    - name: "TFE_REDIS_SIDEKIQ_USE_MTLS"
      value: "<To use mtls with Redis Enterprise? eg. "false">"
    - name: "TFE_REDIS_SIDEKIQ_CLIENT_CERT_PATH"
      value: "<Path to the client certificate file to be used for mTLS authentication with Redis server>"
    - name: "TFE_REDIS_SIDEKIQ_CA_CERT_PATH"
      value: "<Path to the Certificate Authority file user to validate the certificate>"
    - name: "TFE_REDIS_SIDEKIQ_CLIENT_KEY_PATH"
      value: "<Path to the private key file corresponding to the client certificate.>"
    - name: "TFE_REDIS_SENTINEL_ENABLED"
      value: "<To use sentinel? e.g. false>"
    - name: "TFE_REDIS_SENTINEL_HOSTS"
      value: "<Hostname and port of Sentinel hosts, e.g. sentinel.example.com:26379>"
    - name: "TFE_REDIS_SENTINEL_LEADER_NAME"
      value: "<Name of the Sentinel leader>"

      # Vault cluster settings.
      # If you are using the default internal vault, this should be the private routable IP address of the node itself.
    - name: "TFE_VAULT_CLUSTER_ADDRESS"
      value: "https://10.0.66.189:8201"

    image: "images.releases.hashicorp.com/hashicorp/terraform-enterprise:<vYYYYMM-#>"
    name: "terraform-enterprise"
    ports:
    - containerPort: 8080
      hostPort: 80
    - containerPort: 8443
      hostPort: 443
    - containerPort: 8201
      hostPort: 8201
    - containerPort: 9090
      hostPort: 9090
    securityContext:
      capabilities:
        add:
        - "CAP_IPC_LOCK"
      readOnlyRootFilesystem: true
      seLinuxOptions:
        type: "spc_t"
    volumeMounts:
    - mountPath: "/etc/ssl/private/terraform-enterprise"
      name: "certs"
    - mountPath: "/var/log/terraform-enterprise"
      name: "log"
    - mountPath: "/run"
      name: "run"
    - mountPath: "/tmp"
      name: "tmp"
    - mountPath: "/run/docker.sock"
      name: "docker-sock"
    - mountPath: "/var/cache/tfe-task-worker/terraform"
      name: "terraform-enterprise_terraform-enterprise-cache-pvc"
  restartPolicy: "Never"
  volumes:
  - hostPath:
      path: "<path_to_certs_on_host>"
      type: "Directory"
    name: "certs"
  - emptyDir:
      medium: "Memory"
    name: "log"
  - emptyDir:
      medium: "Memory"
    name: "run"
  - emptyDir:
      medium: "Memory"
    name: "tmp"
  - hostPath:
      path: "/run/podman/podman.sock"
      type: "File"
    name: "docker-sock"
  - name: "terraform-enterprise_terraform-enterprise-cache-pvc"
    persistentVolumeClaim:
      claimName: "terraform-enterprise_terraform-enterprise-cache"

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4