Commit Graph

131 Commits

Author SHA1 Message Date
trujillo-adam 0ac96c7d23
Merge pull request #11930 from hashicorp/docs/admin-partition-updates-1.11.0-misc
added line about wildcard intentions not supported for admin partitions
2022-01-10 07:53:58 -08:00
trujillo-adam d4f9a30927 applied feedback 2022-01-07 15:43:51 -08:00
trujillo-adam 2ff5f50e8c tweaks to the language used in the requirements section 2022-01-05 12:01:10 -08:00
Noel Quiles 1ff6da7cdd
website: Update copy (#11853) 2022-01-04 15:29:46 -05:00
trujillo-adam 8852810eb5 added line about wildcard intentions not supported for admin partitions 2022-01-03 15:31:58 -08:00
saurabh-sp-tripathi 69c19ca9fc Fix typo, Layer 7 is application layer not network 2021-12-22 15:13:56 -08:00
trujillo-adam a08f294602
Merge pull request #11859 from hashicorp/docs/service-mesh-gateways-clarification-for-1.11.0
clarify mesh gateway docs use cases; include admin partition flow
2021-12-22 11:56:11 -08:00
trujillo-adam 52f429db26 fixed bad md syntax 2021-12-22 11:40:26 -08:00
trujillo-adam e5b3be0597 applied feedback 2021-12-22 11:18:06 -08:00
David Yu bd011ab7b6
docs: ExportedServices YAML correction (#11883)
* docs: ExportedServices YAML correction

* Add enterprise alert to CRD index
2021-12-17 11:29:10 -08:00
trujillo-adam 300daff089 additional clarification on upstream configurations for x-dc and x-partition traffic 2021-12-17 09:46:50 -08:00
David Yu 40d97ca926
docs: fix ExportedServices typo on example
Fix typlo
2021-12-17 09:39:55 -08:00
David Yu b272e8517d
add enterprise inline 2021-12-16 20:23:03 -08:00
David Yu 72412ca910
docs: add exported services to overview 2021-12-16 20:20:11 -08:00
David Yu 8bcdb6dfa2
docs: ExportedServices CRD typo and change heading for services (#11845) 2021-12-15 15:51:24 -08:00
trujillo-adam bcfff8fde4 clarify mesh gateway docs use cases; include admin partition flow 2021-12-15 13:11:52 -08:00
Chris S. Kim f76fc6cabe
docs: Update discovery chain compilation results with partition fields (#11835) 2021-12-14 15:37:34 -05:00
Kyle Havlovitz f4010065a7 docs: Update exported-services page to include required Name field 2021-12-14 12:10:30 -08:00
Paul Banks 131897bff6
Merge pull request #11164 from hashicorp/docs/ingress-sds
Document SDS for ingress gateways
2021-12-14 17:32:40 +00:00
freddygv e91509383f Clean up additional refs to partition exports 2021-12-04 15:16:40 -07:00
freddygv 09cdeae13c Move exported-services docs based on new name 2021-12-03 17:47:32 -07:00
freddygv ed6076db26 Rename partition-exports to exported-services
Using a name less tied to partitions gives us more flexibility to use
this config entry in OSS for exports between datacenters/meshes.
2021-12-03 17:47:31 -07:00
Paul Banks 1d85afeed4 Reformatting suggestions from review 2021-12-01 15:35:24 +00:00
Paul Banks d5a93d6b88 Apply suggestions from code review
Co-authored-by: trujillo-adam <47586768+trujillo-adam@users.noreply.github.com>
2021-12-01 15:13:40 +00:00
Paul Banks 46849a63f9 Apply suggestions from code review
Co-authored-by: mrspanishviking <kcardenas@hashicorp.com>
2021-12-01 15:13:40 +00:00
Paul Banks fcfedfdb5d Add documentation for SDS support in ingress gateways. 2021-12-01 15:13:40 +00:00
John Cowen b5c8af4580
ui: Add `Service.Partition` as available variable for dashboard urls (#11654) 2021-12-01 11:05:57 +00:00
trujillo-adam cef938e620
Merge pull request #11558 from hashicorp/docs/admin-partitions-service-exports-configuration-entry
Admin partition docs: cross-partition support beta2/3
2021-11-30 11:22:30 -08:00
trujillo-adam 0fb360211a addtional feedback; added PartitionExports to CRDs section 2021-11-30 11:18:12 -08:00
trujillo-adam 632e4bd35c applied additional feedback 2021-11-29 13:28:05 -08:00
David Yu 29c791c90e
docs: Notes about WAN Federation when using Vault as Connect CA (#11143)
* docs: Notes about WAN Federation when using Vault as Connect CA

* Apply suggestions from code review

Co-authored-by: Daniel Nephin <dnephin@hashicorp.com>

* Update website/content/docs/connect/ca/vault.mdx

Co-authored-by: Daniel Nephin <dnephin@hashicorp.com>

* Update website/content/docs/connect/ca/vault.mdx

Co-authored-by: trujillo-adam <47586768+trujillo-adam@users.noreply.github.com>

* Update website/content/docs/connect/ca/vault.mdx

Co-authored-by: trujillo-adam <47586768+trujillo-adam@users.noreply.github.com>

* Update vault.mdx

* Update vault.mdx

Co-authored-by: Daniel Nephin <dnephin@hashicorp.com>
Co-authored-by: trujillo-adam <47586768+trujillo-adam@users.noreply.github.com>
2021-11-29 12:37:14 -08:00
Karl Cardenas d4cbe68913
docs: updated proxy page to use new codeblock 2021-11-18 18:17:38 -07:00
Iryna Shustava 0ee456649f
connect: Support auth methods for the vault connect CA provider (#11573)
* Support vault auth methods for the Vault connect CA provider
* Rotate the token (re-authenticate to vault using auth method) when the token can no longer be renewed
2021-11-18 13:15:28 -07:00
trujillo-adam e4d89b4214 fixed typo and added link from partition exports to admin partitions section 2021-11-17 08:50:07 -08:00
trujillo-adam 6b8225c6f1 fixed bad links 2021-11-16 12:05:18 -08:00
trujillo-adam e2ac4c8a30 added link to agent configuration from partition exports in usage section 2021-11-16 10:53:07 -08:00
trujillo-adam 756e65cbcb applied freddy's feedback 2021-11-16 10:44:21 -08:00
trujillo-adam 91e44f488d Adding partition exports configuraiton entry details, upstream config, acl impact 2021-11-13 18:52:58 -08:00
trujillo-adam caf850e135 first commit for cross-partition support - partition exports section 2021-11-11 18:43:57 -08:00
mrspanishviking b8e11507b1
Merge pull request #11543 from hashicorp/envoy-token
docs: added more information to help endusers with proxies and ACL
2021-11-11 08:37:12 -08:00
mrspanishviking f1b4a10c83
Update website/content/docs/connect/proxies/integrate.mdx
Co-authored-by: trujillo-adam <47586768+trujillo-adam@users.noreply.github.com>
2021-11-11 08:05:45 -08:00
mrspanishviking 42ab9e8aa4
Update website/content/docs/connect/ca/vault.mdx
Co-authored-by: Daniel Nephin <dnephin@hashicorp.com>
2021-11-10 13:03:28 -08:00
Karl Cardenas 50ff9e8a6e
docs: added more information to help endusers with proxies and ACL tokens 2021-11-10 08:52:44 -07:00
Karl Cardenas 5644edae5c
docs: added link to the Learn tutorial in Vault CA integration page 2021-11-10 07:30:12 -07:00
Freddy 5e7eb85f2a
Fix caveat about resolvers operating at L4 (#11497)
Service resolvers can specify L4 rules such as redirects, or L7 rules such as
hash-based load balancing policies.
2021-11-08 07:11:36 -07:00
Connor efe4b21287
Support Vault Namespaces explicitly in CA config (#11477)
* Support Vault Namespaces explicitly in CA config

If there is a Namespace entry included in the Vault CA configuration,
set it as the Vault Namespace on the Vault client

Currently the only way to support Vault namespaces in the Consul CA
config is by doing one of the following:
1) Set the VAULT_NAMESPACE environment variable which will be picked up
by the Vault API client
2) Prefix all Vault paths with the namespace

Neither of these are super pleasant. The first requires direct access
and modification to the Consul runtime environment. It's possible and
expected, not super pleasant.

The second requires more indepth knowledge of Vault and how it uses
Namespaces and could be confusing for anyone without that context. It
also infers that it is not supported

* Add changelog

* Remove fmt.Fprint calls

* Make comment clearer

* Add next consul version to website docs

* Add new test for default configuration

* go mod tidy

* Add skip if vault not present

* Tweak changelog text
2021-11-05 11:42:28 -05:00
FFMMM fdb0ee6093
change vault ca docs to mention root cert ttl config (#11488)
Signed-off-by: FFMMM <FFMMM@users.noreply.github.com>
2021-11-04 15:44:22 -07:00
Luke Kysow 9b680b3f81
Add quick-link for users coming from UI (#11403)
The Consul UI topology view has an icon with the text
"Configure metrics dashboard" that links to this page. Add a notice at
the top of the page that links them directly to the relevant section.
2021-11-03 09:37:30 -07:00
Luke Kysow 7eb32cdb73
Remove Name/Namespace fields from upstream default (#11456)
The UpstreamConfig.Defaults field does not support setting Name or
Namespace because the purpose is to apply defaults to all upstreams.
I think this was just missed in the docs since those fields would
error if set under Defaults.

i.e. this is not supported:

```
UpstreamConfig {
  Defaults {
    Name = "foo"
    Namespace = "bar"
    # Defaults config here
  }
}
```
2021-11-02 14:21:15 -07:00
Evan Culver bec08f4ec3
connect: Add support for Envoy 1.20 (#11277) 2021-10-27 18:38:10 -07:00