cdk-kubesphere
cdk-kubesphere is a CDK construct library that allows you to create KubeSphere on AWS with CDK in TypeScript, JavaScript or Python.
Sample
import { KubeSphere } from 'cdk-kubesphere';
const app = new cdk.App();
const stack = new cdk.Stack(app, 'cdk-kubesphere-demo');
// deploy a default KubeSphere service on a new Amazon EKS cluster
new KubeSphere(stack, 'KubeSphere');
Behind the scene, the KubeSphere construct creates a default Amazon EKS cluster and KubeSphere serivce with helm chart(ks-installer) on it.
View helm command
AWS CDK will helm install the `ks-installer` on the cluster:helm install ks-installer \
--repo https://charts.kubesphere.io/test \
--namespace=kubesphere-system \
--generate-name \
--create-namespace
KubeSphere App Store
Use appStore to enable the KubeSphere App Store support.
new KubeSphere(stack, 'KubeSphere', {
appStore: true,
});
View helm command
AWS CDK will helm install the `ks-installer` on the cluster:helm install ks-installer \
--set openpitrix.enabled=true \
--repo https://charts.kubesphere.io/test \
--namespace=kubesphere-system \
--generate-name \
--create-namespace
Using existing Amazon EKS clusters
You are allowed to deploy KubeSphere in any existing Amazon EKS cluster.
const cluster = eks.Cluster.fromClusterAttributes(this, 'MyCluster', {
clusterName: 'my-cluster-name',
kubectlRoleArn: 'arn:aws:iam::1111111:role/iam-role-that-has-masters-access',
});
// deploy a default KubeSphere service on the existing Amazon EKS cluster
new KubeSphere(stack, 'KubeSphere', { cluster });
See Using existing clusters to learn how to import existing cluster in AWS CDK.
Console
Run the following command to create a port-forward from localhost:8888 to ks-console:80
kubectl -n kubesphere-system port-forward service/ks-console 8888:80
Open http://localhost:8888 and enter the default username/password(admin/P@88w0rd) to enter the admin console.
1 maintainer
Metadata
1 maintainer
Release files for cdk-kubesphere 2.0.315
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| cdk-kubesphere-2.0.315.tar.gz | 31.6 kB | Without provenance | Details for cdk-kubesphere-2.0.315.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cdk_kubesphere-2.0.315-py3-none-any.whl | Python 3 | none | any | Details for cdk_kubesphere-2.0.315-py3-none-any.whl |
Total release size: 61.7 kB
Release files / cdk-kubesphere-2.0.315.tar.gz
| Download URL | cdk-kubesphere-2.0.315.tar.gz |
|---|---|
| Size | 31.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0244f5f69e051683fa6133b90dd6ddc24aaedd29231ef83ff6fa9676d1ba175d
|
|
BLAKE2b-256 checksum How to use checksums |
bc32a1b360f73bb2d8562dc6f1ad1421807a9a2fb42904dd61664ec389da2848
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.2
|
Release files / cdk_kubesphere-2.0.315-py3-none-any.whl
| Download URL | cdk_kubesphere-2.0.315-py3-none-any.whl |
|---|---|
| Size | 30.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c4d979558fb0818d8ca24199d2ea5912b4b218e34682ce42d9c207eb11de5ce6
|
|
BLAKE2b-256 checksum How to use checksums |
df22132f513bebbb6e52b9631687f7cef4d47e2f2f66e5ed54538c294ef85292
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.2
|
Security for cdk-kubesphere 2.0.315
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
