This repository has been archived by the owner on Oct 27, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 16
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
change kubepath to take the raw bytes of the file (#11)
* change kube_path to kube_file to take raw file text
- Loading branch information
Showing
8 changed files
with
128 additions
and
34 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,22 +1,47 @@ | ||
# Terraform Provider for Gardener Examples | ||
|
||
## Overview | ||
|
||
This folder contains a set of examples which use Gardener services to deploy [AWS](https://github.com/kyma-incubator/terraform-provider-gardener/tree/master/examples/aws), [GCP](https://github.com/kyma-incubator/terraform-provider-gardener/tree/master/examples/gcp) and [Azure](https://github.com/kyma-incubator/terraform-provider-gardener/tree/master/examples/azure) clusters. All provided examples have the following section in common: | ||
|
||
```bash | ||
provider "gardener" { | ||
kube_path = "<my-gardener-service-account-kubeconfig>" | ||
} | ||
``` | ||
This section includes the following parameters: | ||
* **kube_path** - the path for the kubeconfig file of the service bot of the profile. | ||
|
||
## Installation | ||
|
||
Follow these steps to run an example: | ||
|
||
1. Clone the `terraform-provider-gardener` repository. | ||
2. Go to `terraform-provider-gardener/examples/{example_name}`. | ||
3. Run `terraform apply`. | ||
|
||
# Terraform Provider for Gardener Examples | ||
|
||
## Overview | ||
|
||
This folder contains a set of examples which use Gardener services to deploy [AWS](https://github.com/kyma-incubator/terraform-provider-gardener/tree/master/examples/aws), [GCP](https://github.com/kyma-incubator/terraform-provider-gardener/tree/master/examples/gcp) and [Azure](https://github.com/kyma-incubator/terraform-provider-gardener/tree/master/examples/azure) clusters. All provided examples have the following section in common: | ||
|
||
```bash | ||
provider "gardener" { | ||
kube_file = "${file("<my-gardener-service-account-kubeconfig>")}" | ||
} | ||
``` | ||
You can pass the kube_file using the raw text alone as follows: | ||
```bash | ||
kube_file =<<-EOT | ||
kind: Config | ||
clusters: | ||
- cluster: | ||
certificate-authority-data: >- | ||
<certificate-authority-data> | ||
server: "https://gardener.garden.canary.k8s.ondemand.com" | ||
name: garden | ||
users: | ||
- user: | ||
token: >- | ||
<token> | ||
name: robot | ||
contexts: | ||
- context: | ||
cluster: garden | ||
user: robot | ||
namespace: garden-<profile> | ||
name: garden-<profile>-robot | ||
current-context: garden-<profile>-robot | ||
EOT | ||
``` | ||
This section includes the following parameters: | ||
* **kube_file** - the raw string of the kube config file. | ||
## Installation | ||
Follow these steps to run an example: | ||
1. Clone the `terraform-provider-gardener` repository. | ||
2. Go to `terraform-provider-gardener/examples/{example_name}`. | ||
3. Run `terraform apply`. | ||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters