datawire/Telepresence Intercept
Intercepts a service in a remote cluster
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stalelast commit Jun 1, 2022
- License
- None
Pinned Snippet
uses: datawire/development-telepresence-intercept@4ec8eec9409a61af222d8b33b67bccc8089cf12c # v0.110tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| telepresence_api_key | API KEY to login in app.getambassador.io | yes | — |
| service_name | The name of the ervice to intercept | yes | — |
| service_port | The port to intercept | yes | — |
| kubeconfig_file | Content of the kubernetes configuration used with kubectl | yes | — |
| namespace | The namespace of the service to intercept | no | default |
| http_header | Only intercept traffic that matches this "HTTP2_HEADER=REGEXP" specifier | no | x-telepresence-intercept-id=service-intercepted |
| env_file | Emit the remote environment to an env file in Docker Compose format | no | — |
| ingress_host | This value will be used as the ingress hostname | no | ambassador.ambassador |
| ingress_port | This value will be used as the ingress port | no | 80 |
| ingress_tls | This flag will determine if TLS is used, and will default to false. | no | — |
| ingress_l5 | This flag will default to the ingress-host value. | no | ambassador.ambassador |
Outputs
no outputs