-
Hey @costela
I would like to propose extending ip-floater to support other clouds.
This could be done gradually based on provider support and ease of implementation.
We could probably start with t…
-
### What feature would you like to have in the provider?
It would be nice to have the capability to attach the created volume to a specific instance or server.
e.g.
```
resource "exoscale_block_…
-
**Is your feature request related to a problem? Please describe.**
Currently on cloud providers, loxiLB offers HA within the same region and multi-AZs. This doesnt protect us from regional disasters.…
-
### What happened?
We found go vet issues of `lostcancel` in #109184. (It seems that go vet checks are not running under `/staging` dir.)
```
staging/src/k8s.io/legacy-cloud-providers/vsphere/n…
-
## Motivations
Whenever we need to communicate with some sort of (cloud) service, authentication is usually a requirement. The means of authentication of course depend on the cloud / identity provi…
-
Currently it seems only one property gets populated:
```
type: Entity
api_version: core/v2
metadata:
name: ip-10-12-20-4
spec:
system:
cloud_provider: EC2
```
## Feature Suggesti…
-
Use Terraform to create infrastructure on different providers with a click.
Requirements:
1. Terraform definition to create the Kubernetes cluster of all SATP infrastructure (gateway, databases, U…
-
This is an open ended meta issue. If there is a better place to discuss this please let me know.
I notice that there are several different Vault Terraform projects for AWS, GCP, and Azure. (And oth…
-
Our cloud-controller-manager documentation is pages and blogs mention the following components that need to be configured for external cloud providers:
- kube-apiserver
- kube-controller-manager
- ku…
-
## Tell us about the problem you're trying to solve
Today we only support S3. Implement this for the other cloud providers.
## Describe the solution you’d like
- [x] GCS logging
- [ ] Azure logg…