Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixes #14 Dedicated cluster network options and encryption key #23

Closed
wants to merge 2 commits into from
Closed

Fixes #14 Dedicated cluster network options and encryption key #23

wants to merge 2 commits into from

Conversation

PhilGrayson
Copy link

@PhilGrayson PhilGrayson commented Sep 24, 2021

Fixes #14.

  • Expose option to define a dedicated cluster's network option (Internet, Private Link, VPC Peering)
  • Expose option to define a dedicated cluster's encryption key

This was discovered by submitting a cluster creation request via https://confluent.cloud UI and inspecting the POST body to https://confluent.cloud/api/clusters. This is what the body looks like:

    {
      "config": {
        "name": "cluster_2",
        "account_id": "env-12345",
        "network_ingress": 100,
        "network_egress": 100,
        "storage": 500,
        "durability": "LOW",
        "region": "eu-west-1",
        "service_provider": "aws",
        "organization_id": 12345,
        "deployment": {
          "sku": "DEDICATED",
          "account_id": "env-12345"
        },
        "cku": 1,
        "selected_network_type": "PRIVATE_LINK",
        "encryption_key_id": "arn:aws:kms:eu-west-1:000000000000:key/0000000000000-1111-2222-333333333333"
      }
    }

Current valid options for AWS are:
  - PUBLIC
  - PRIVATE_LINK
  - VPC_PEERING

This is only tested in AWS. Here is a POST body to https://confluent.cloud/api/clusters
setting Private Link networking.

    {
      "config": {
        "name": "cluster_2",
        "account_id": "env-12345",
        "network_ingress": 100,
        "network_egress": 100,
        "storage": 500,
        "durability": "LOW",
        "region": "eu-west-1",
        "service_provider": "aws",
        "organization_id": 12345,
        "deployment": {
          "sku": "DEDICATED",
          "account_id": "env-12345"
        },
        "cku": 1,
        "selected_network_type": "PRIVATE_LINK",
        "encryption_key_id": "arn:aws:kms:eu-west-1:000000000000:key/0000000000000-1111-2222-333333333333"
      }
    }
https://docs.confluent.io/cloud/current/clusters/byok/index.html

This is only tested in AWS. This is POST body to https://confluent.cloud/api/clusters
setting an ecryption key.

    {
      "config": {
        "name": "cluster_2",
        "account_id": "env-12345",
        "network_ingress": 100,
        "network_egress": 100,
        "storage": 500,
        "durability": "LOW",
        "region": "eu-west-1",
        "service_provider": "aws",
        "organization_id": 12345,
        "deployment": {
          "sku": "DEDICATED",
          "account_id": "env-12345"
        },
        "cku": 1,
        "selected_network_type": "PRIVATE_LINK",
        "encryption_key_id": "arn:aws:kms:eu-west-1:000000000000:key/0000000000000-1111-2222-333333333333"
      }
    }
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support Networking options as part of the ClusterCreateConfig
1 participant