nia/docs 0.1.0 ga (#9946)

* docs/nia: consul compatibilty

* docs/nia: remove beta callouts (#9919)

Co-authored-by: Kim Ngo <6362111+findkim@users.noreply.github.com>
This commit is contained in:
lornasong 2021-03-29 15:23:10 -04:00 committed by GitHub
parent d38b04e96b
commit 6dd378b603
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
6 changed files with 24 additions and 5 deletions

View File

@ -0,0 +1,18 @@
---
layout: docs
page_title: Consul-Terraform-Sync Compatibility
sidebar_title: Compatibility
description: >-
Consul-Terraform-Sync Compatibility
---
# Compatibility
## Consul
Below are the supported Consul versions with compatible Consul-Terraform-Sync versions. The latest Consul-Terraform-Sync binary targets supporting the latest patch version of the three most recent Consul minor versions.
| Consul Version | Compatible Consul-Terraform-Sync Version |
| ------------------------------------ | ---------------------------------------- |
| Latest patch version of 1.9 | 0.1.0 |
| Latest patch version of 1.8 (1.8.9) | 0.1.0 |
| Latest patch version of 1.7 (1.7.13) | 0.1.0 |

View File

@ -1,12 +1,12 @@
---
layout: docs
page_title: Network Infrastructure Automation
sidebar_title: Network Infrastructure Automation <sup>Beta</sup>
sidebar_title: Network Infrastructure Automation
description: >-
Network Infrastructure Automation (NIA) is the concept of dynamically updating infrastructure devices triggered by service changes. Consul-Terraform-Sync is a tool that performs NIA and utilizes Consul as a data source that contains networking information about services and monitors those services. Terraform is used as the underlying automation tool and leverages the Terraform provider ecosystem to drive relevant changes to the network infrastructure.
---
# Network Infrastructure Automation <sup>Beta</sup>
# Network Infrastructure Automation
Network Infrastructure Automation (NIA) enables dynamic updates to network infrastructure devices triggered by service changes. Consul-Terraform-Sync utilizes Consul as a data source that contains networking information about services and monitors those services. Terraform is used as the underlying automation tool and leverages the Terraform provider ecosystem to drive relevant changes to the network infrastructure.

View File

@ -20,6 +20,8 @@ Consul-Terraform-Sync is a daemon that runs alongside Consul, similar to other C
To install a local Consul agent, refer to the [Getting Started: Install Consul Tutorial](https://learn.hashicorp.com/tutorials/consul/get-started-install).
For information on compatible Consul versions, refer to the [Consul compatibility matrix](/docs/nia/compatibility#consul).
### Run an Agent
The Consul agent must be running in order to dynamically update network devices. To run the local Consul agent, you can run Consul in development mode which can be started with `consul agent -dev` for simplicity. For more details on running Consul agent, refer to the [Getting Started: Run the Consul Agent Tutorial](https://learn.hashicorp.com/tutorials/consul/get-started-agent?in=consul/getting-started).

View File

@ -8,8 +8,6 @@ description: >-
# Compatible Terraform Modules for Network Infrastructure Automation
-> **Note:** Consul-Terraform-Sync is currently in Beta. Specifications in this section may change going into the General Availability release.
Consul-Terraform-Sync automates execution of Terraform modules through tasks. A task is a construct in Consul-Terraform-Sync that defines the automation of Terraform and the module.
## Module Specifications

View File

@ -1,7 +1,7 @@
---
layout: docs
page_title: Consul NIA Security Model
sidebar_title: Network Infrastructure Automation <sup>Beta</sup>
sidebar_title: Network Infrastructure Automation
description: >-
Security model including requirements, recommendations, and threats for Consul Network Infrastructure Automation (NIA).
---

View File

@ -237,6 +237,7 @@ export default [
'tasks',
'terraform-modules',
'network-drivers',
'compatibility',
],
},