* Fix bug in opsgenie plugin mixing up notify-services and schedules
* Update docs for opsgenie plugin to use correct schedules
* Remove accidental change to opsgenie client
* Update opsgenie client tests
* Update backend reference with working proxy configuration
the local loopback does not work in this case. After discussing internally, recommendation is to use 0.0.0.0 for the diag addr but with a warning this should NOT be exposed to the public internet or used on other instances
* Update backends.mdx
* Update docs/pages/reference/backends.mdx
Co-authored-by: Steven Martin <steven@goteleport.com>
* Update docs/pages/reference/backends.mdx
Co-authored-by: Zac Bergquist <zac.bergquist@goteleport.com>
* Update backends.mdx
* Update docs/pages/reference/backends.mdx
Co-authored-by: Zac Bergquist <zac.bergquist@goteleport.com>
---------
Co-authored-by: Steven Martin <steven@goteleport.com>
Co-authored-by: Zac Bergquist <zac.bergquist@goteleport.com>
* docs: Use different versions of Teleport Windows auth package for Team/Cloud
* Combine OSS/Enterprise and Team/Cloud for tidiness
* Disable lint for out-of-order markers
Using the regular 1. 1. 1. style does not work when broken by tabs
* Recommend on-demand mode and continuous backups in DynamoDB docs
Removes mention to provisioned mode and manually setting capacity
in favor of using on-demand mode. Enabling continuous backups was
also elevated into the main configuration reference since they are
strongly encouraged.
Additionally all occurrences of `back-end` were replaced with
`backend` to be consistent with all other usages.
* remove autoscaling references from aws chart docs
* Add a guide for setting up Access Graph on-prem
* Update docs/pages/access-graph/getting-started-on-prem.mdx
Co-authored-by: Tiago Silva <tiago.silva@goteleport.com>
* Update minimum required Teleport version
* Address review suggestions
* Note support for Amazon RDS
* Add a note about Teleport Policy
* Move license requirement to "Prerequisites"
* Bump TAG version in docs
* Address review comments
* Update docs/pages/access-graph/getting-started-on-prem.mdx
Co-authored-by: Zac Bergquist <zac.bergquist@goteleport.com>
* Update Access Graph menu item image
* Update wording in Teleport Team notice
* Expand on requirements for the TLS certificate
* Apply suggestions from code review
Co-authored-by: Paul Gottschling <paul.gottschling@goteleport.com>
* Move access-graph pages under access-controls
* Get rid of extraneous tags
* Add a short introduction to the guide
* Elaborate where the TAG config should live
* nit
* Rename the TAG self-hosted guide
* Fix image paths after access-graph renaming
---------
Co-authored-by: Tiago Silva <tiago.silva@goteleport.com>
Co-authored-by: Zac Bergquist <zac.bergquist@goteleport.com>
Co-authored-by: Paul Gottschling <paul.gottschling@goteleport.com>
This commit updates the `cert-manager` installation instructions to configure the `cert-manager` leader election to use `cert-manager` namespace instead of `kube-system`.
This is required because in GCP Autopilot clusters lock down access to `kube-system` and helm installation can't be successful.
By default, `cert-manager` uses `kube-system` as leader election to prevent multiple parallel installations of `cert-manager` in the same cluster, but if it's already running in the target cluster, the installation will fail with a non clear error. Given the above, it's preferred to use a separate namespace for leader election to prevent races.
Fixes#25312
Signed-off-by: Tiago Silva <tiago.silva@goteleport.com>
* fix indentation of note in mongo guide
* note redis version limits next to version prereq
* extract custom db tls CA snippet from MongoDB
* update pre-reqs for self-hosted cluster databases
* expand tls config setup in CockroachDB guide
* remove redis cluster tls-cluster no config tab
This config still requires a custom CA, so it's pointless
and less secure.
It also doesn't work with the rest of the guide steps currently.
* use code block instead of sh in redis cluster doc
* dont explain tctl auth sign setup when unused
* fix redis-cluster code block
* describe teleport trust setup last
* clarify cluster creation certs
* use more descriptive tab labels for cockroachdb
* only mention lack of support for RESP3
redis 7.0 is supported with RESP2, no need to call it out.
* docs: update docker installation for distroless info
* remove version change info for distroless
* add instrs on interacting with distroless
* Update language
Co-authored-by: Paul Gottschling <paul.gottschling@goteleport.com>
* Update installation.mdx
Co-authored-by: Paul Gottschling <paul.gottschling@goteleport.com>
---------
Co-authored-by: Paul Gottschling <paul.gottschling@goteleport.com>
From `docs/postrelease.md`:
- [x] Update `branchMajorVersion` const in Dronegen `/dronegen/container_images.go`, then run `make dronegen`
- [x] Update `CURRENT_VERSION_ROOT`, `PREVIOUS_VERSION_ONE_ROOT`, and `PREVIOUS_VERSION_TWO_ROOT` variables in `.drone.yml`, then run `make dronegen`
- Example: https://github.com/gravitational/teleport/pull/4602
- [x] Create PR to update default Teleport image referenced in docker/teleport-quickstart.yml
- Example: https://github.com/gravitational/teleport/pull/4655
- [x] Create PR to update default Teleport image referenced in docker/teleport-lab.yml
* [docs] IAM-auth-as-IAM-roles for Redshift
* new section for iam role auth
* clarify two methods
* review comments
* fix spelling, thanks to docs lint!
Closes#37106
- Add a section re: IGS and move applicable row items into it
- Rename "Open Source" to "Community Edition" in line with guidance
- Alphabetize sections and rows within each section
- Fix a minor error in the Prerequisites section that refers to the
"prerequisites above" when they are, in fact, below.
- Update the resource view screenshot.
- Update the explanation of the UI flow for enrolling a new resource.
* Move Connect My Computer section after sections dedicated to resources
Connect My Computer is not that important to have it before sections
dedicated to different kinds of resources.
* Adjust existing resource sections to changes brought by Unified Resources
* Add docs for application access in Connect
* Update link to docs in app gateway document
* Update supported app kinds
* Update instructions based on recent UI changes
* HTTP apps -> web apps
* Update docs version mentions to reflect v15
- Remove mentions of pre-v12 versions. We mention the version prior to
the earliest supported version in case some users still need to
upgrade.
This includes removing the Helm migration guide from v11 to v12. The
idea is that Teleport users should be on v12 already (the earliest
supported version before we released v15), so this guide should not be
needed.
- Updated the supported version table in the FAQ.
* Respond to feedback
Restore the v12 migration guide with a note to remove it in v16.
* Update usage docs with the reporting endpoint
adding the actual reporting endpoint to our public docs for customers who need to whitelist a specific outbound reporting endpoint
* Update docs/pages/usage-billing.mdx
Co-authored-by: Zac Bergquist <zac.bergquist@goteleport.com>
* Update cspell.json
fix lint issue
---------
Co-authored-by: Zac Bergquist <zac.bergquist@goteleport.com>
- Update instructions and images to match the v15 UI.
- Minor readability improvements.
- Replace `mytenant` with `example` in example URLs since we're phasing
out the "tenant" language.
* Add an overview of the Teleport documentation
Closes#34038
Help visitors to the Teleport documentation find their way through the
docs site by including a description of each docs page in an overview
guide.
This change is based on adapting the former Teleport index page (prior
to #27703).
* Minor grammar and language tweaks
* saml attribute mapping reference
* formatting
* rename test_attribute_mapping to test-attribute-mapping
* - copy edits
- update add method to show set().add() and set(values) syntax
- update strings.split() syntax
* address review comments:
- move prerequisite up
- remove description from predicate evaluation context table
- copy edits
* - add attribute mapping reference to idp.mdx (root page)
- add a line explaining the context of the page
- move attribute mapping context inside Predicate expressions heading
- remove tctl reference
* revert previous commit on saml-attribute-mapping.mdx
* - move concept to top of the page
- add tctl reference back
* single identation for sub nesting
* single indent for attribute mapping name format
* update saml reference copy on idp.mdx (root page)
We removed this feature in v15, so remove the guide from the docs and
add a redirect. v14 users can refer to v14 of the docs, which includes
the guide along with a deprecation notice.
Based on following the guide per the v15 test plan:
- Be more explicit that we expect the `member` role to be defined in a
file called `member.yaml`.
- Be more explicit re: replacing the `myuser` variable with the name of
your user.
* Remove account lockout from failed recovery attempts
This account lockout looks to be unecessary and potentially problematic. Recovery codes and recovery through MFA are not possible to brute force.
In addition the potential to lockout an account from being able to use a recovery method could result in them being unable to unlock their account from other potential abuse cases (for example an attacker locking the account from failed password attempts).
As discussed in the RFD (https://github.com/gravitational/teleport/pull/35533) this includes the removal of all the API used for this locking mechanism.
* accountrecovery: Update `WithLock` function names
* accountrecovery: Combine verifyRecoveryCode and verifyRecoveryCodeWithRecord into one function
* Further GRPC cleanup after PR feedback
* Apply PR Feedback
* docs: Fix description of location of -fips suffix on AMIs
The `-fips` suffix appears after the `<arch>` component, not before as I
previously documented in 1548a43 (I saw some v15 dev builds with -fips
after the version, but they were from before <arch> was added).
This can be seen with:
aws --region us-west-2 ec2 describe-images --owners 146628656107 --filters 'Name=name,Values=teleport-ent-15.0.0-alpha.5-*-fips-*'
* docs: Add example for FIPS AMI
* add service provider with entity id and acs url. make entity descriptor optional config
* move dedicate role creation to end of the guide
* review comments:
- copy edits
- use add-role-to-user.mdx to reference role update
* reference content of entity descrptor takes priority over other values
* copy edits:
- use lower case for service provider
- use generic service provider name instead of directly referencing samltest.id
- update test saml application copy
* fix typo
Brian Joerger