├── static ├── .nojekyll ├── img │ ├── avesha.png │ ├── Architecture-OS.png │ ├── Kindclusters-OS.png │ ├── Bookinfo-productpage-OS.png │ ├── Namespace-Isolation-OS.png │ ├── community-register-free.png │ ├── kubeslice-illustration.png │ ├── x.svg │ ├── youtube.svg │ ├── linked-in.svg │ └── slack.svg └── font │ └── CherryBomb-Regular.ttf ├── .dockerignore ├── .github ├── ISSUE_TEMPLATE │ ├── config.yml │ ├── FEATURE.yaml │ └── ISSUE.yml └── workflows │ ├── spellcheck.yml │ └── trivy.yaml ├── babel.config.js ├── images └── images │ ├── kubeslice-cli │ └── mac-download.png │ ├── version1.0.0 │ ├── monitor │ │ ├── add-to-slack.png │ │ ├── slack-installed-apps.png │ │ ├── slack-webhook-save.png │ │ ├── slack-copy-webhook-url.png │ │ ├── slack-post-to-channel.png │ │ ├── slack-channel-admin-option.png │ │ └── slack-add-incoming-webhook-integration.png │ └── monitoring-events │ │ ├── ksm-events.png │ │ ├── app-level-token.png │ │ ├── create-channel1.png │ │ ├── add-bot-to-channel.png │ │ ├── bot-user-oauth-token.png │ │ ├── botkube-app-in-slack.png │ │ ├── copy-app-level-token.png │ │ ├── kubernetes-events1.png │ │ ├── kubernetes-events2.png │ │ ├── kubernetes-events3.png │ │ ├── kubernetes-events4.png │ │ ├── kubernetes-events5.png │ │ ├── generate-app-level-token.png │ │ ├── kubeslice-worker-events.png │ │ └── kubeslice-controller-events.png │ ├── version1.1.0 │ ├── monitor │ │ ├── add-to-slack.png │ │ ├── slack-installed-apps.png │ │ ├── slack-webhook-save.png │ │ ├── slack-copy-webhook-url.png │ │ ├── slack-post-to-channel.png │ │ ├── slack-channel-admin-option.png │ │ └── slack-add-incoming-webhook-integration.png │ └── monitoring-events │ │ ├── ksm-events.png │ │ ├── app-level-token.png │ │ ├── create-channel1.png │ │ ├── add-bot-to-channel.png │ │ ├── bot-user-oauth-token.png │ │ ├── botkube-app-in-slack.png │ │ ├── copy-app-level-token.png │ │ ├── kubernetes-events1.png │ │ ├── kubernetes-events2.png │ │ ├── kubernetes-events3.png │ │ ├── kubernetes-events4.png │ │ ├── kubernetes-events5.png │ │ ├── generate-app-level-token.png │ │ ├── kubeslice-worker-events.png │ │ └── kubeslice-controller-events.png │ ├── version1.2.0 │ ├── monitor │ │ ├── add-to-slack.png │ │ ├── slack-installed-apps.png │ │ ├── slack-webhook-save.png │ │ ├── slack-copy-webhook-url.png │ │ ├── slack-post-to-channel.png │ │ ├── slack-channel-admin-option.png │ │ └── slack-add-incoming-webhook-integration.png │ ├── monitoring-events │ │ ├── ksm-events.png │ │ ├── app-level-token.png │ │ ├── create-channel1.png │ │ ├── add-bot-to-channel.png │ │ ├── bot-user-oauth-token.png │ │ ├── botkube-app-in-slack.png │ │ ├── copy-app-level-token.png │ │ ├── kubernetes-events1.png │ │ ├── kubernetes-events2.png │ │ ├── kubernetes-events3.png │ │ ├── kubernetes-events4.png │ │ ├── kubernetes-events5.png │ │ ├── generate-app-level-token.png │ │ ├── kubeslice-worker-events.png │ │ └── kubeslice-controller-events.png │ └── key-features │ │ └── support-for-private-clusters.png │ ├── version1.3.0 │ ├── monitor │ │ ├── add-to-slack.png │ │ ├── slack-installed-apps.png │ │ ├── slack-webhook-save.png │ │ ├── slack-copy-webhook-url.png │ │ ├── slack-post-to-channel.png │ │ ├── slack-channel-admin-option.png │ │ └── slack-add-incoming-webhook-integration.png │ ├── monitoring-events │ │ ├── ksm-events.png │ │ ├── app-level-token.png │ │ ├── create-channel1.png │ │ ├── add-bot-to-channel.png │ │ ├── bot-user-oauth-token.png │ │ ├── botkube-app-in-slack.png │ │ ├── copy-app-level-token.png │ │ ├── kubernetes-events1.png │ │ ├── kubernetes-events2.png │ │ ├── kubernetes-events3.png │ │ ├── kubernetes-events4.png │ │ ├── kubernetes-events5.png │ │ ├── generate-app-level-token.png │ │ ├── kubeslice-worker-events.png │ │ └── kubeslice-controller-events.png │ ├── use-cases │ │ └── configure-mongodb │ │ │ ├── overview.png │ │ │ ├── host-mapping.png │ │ │ ├── api-access-list.png │ │ │ ├── app-definition.png │ │ │ ├── create-api-key.png │ │ │ ├── ops-deployment.png │ │ │ ├── ops-manager-db.png │ │ │ ├── ops-manager-ui.png │ │ │ ├── ops-organizations.png │ │ │ ├── save-api-key-info.png │ │ │ ├── ops-access-manager.png │ │ │ ├── add-access-list-entry.png │ │ │ ├── organization-settings.png │ │ │ ├── replicaset-deployment.png │ │ │ ├── replicaset-outside-clusters.png │ │ │ └── replicaset-within-clusters.png │ └── key-features │ │ └── support-for-private-clusters.png │ └── version-1.4.0 │ ├── monitor │ ├── add-to-slack.png │ ├── slack-webhook-save.png │ ├── slack-installed-apps.png │ ├── slack-post-to-channel.png │ ├── slack-copy-webhook-url.png │ ├── slack-channel-admin-option.png │ └── slack-add-incoming-webhook-integration.png │ ├── monitoring-events │ ├── ksm-events.png │ ├── app-level-token.png │ ├── create-channel1.png │ ├── add-bot-to-channel.png │ ├── kubernetes-events1.png │ ├── kubernetes-events2.png │ ├── kubernetes-events3.png │ ├── kubernetes-events4.png │ ├── kubernetes-events5.png │ ├── bot-user-oauth-token.png │ ├── botkube-app-in-slack.png │ ├── copy-app-level-token.png │ ├── generate-app-level-token.png │ ├── kubeslice-worker-events.png │ └── kubeslice-controller-events.png │ ├── use-cases │ └── configure-mongodb │ │ ├── overview.png │ │ ├── app-definition.png │ │ ├── create-api-key.png │ │ ├── host-mapping.png │ │ ├── ops-deployment.png │ │ ├── ops-manager-db.png │ │ ├── ops-manager-ui.png │ │ ├── api-access-list.png │ │ ├── ops-access-manager.png │ │ ├── ops-organizations.png │ │ ├── save-api-key-info.png │ │ ├── add-access-list-entry.png │ │ ├── organization-settings.png │ │ ├── replicaset-deployment.png │ │ ├── replicaset-within-clusters.png │ │ └── replicaset-outside-clusters.png │ └── key-features │ └── support-for-private-clusters.png ├── src ├── theme │ ├── MDXComponents.js │ ├── DocSidebar │ │ ├── index.d.ts │ │ ├── Desktop │ │ │ ├── index.d.ts │ │ │ ├── styles.module.css │ │ │ └── index.js │ │ └── index.js │ ├── Footer │ │ └── index.d.ts │ ├── DocVersionBanner │ │ └── index.d.ts │ └── NotFound │ │ └── Content │ │ └── index.js └── pages │ ├── index.module.css │ └── index.js ├── versioned_docs ├── version-0.2.0 │ ├── release-notes │ │ └── release-notes.mdx │ ├── getting-started-with-cloud-clusters │ │ ├── tutorials │ │ │ └── tutorials.mdx │ │ ├── getting-started-with-cloud-clusters.mdx │ │ ├── installing-kubeslice │ │ │ ├── installing-kubeslice.mdx │ │ │ └── isolating-namespaces.mdx │ │ └── uninstalling-kubeslice │ │ │ ├── uninstalling-kubeslice.mdx │ │ │ ├── deleting-the-slice.mdx │ │ │ └── deleting-the-project.mdx │ └── community.mdx ├── version-0.3.0 │ ├── release-notes │ │ └── release-notes.mdx │ ├── getting-started-with-cloud-clusters │ │ ├── tutorials │ │ │ └── tutorials.mdx │ │ ├── getting-started-with-cloud-clusters.mdx │ │ ├── installing-kubeslice │ │ │ ├── installing-kubeslice.mdx │ │ │ └── isolating-namespaces.mdx │ │ └── uninstalling-kubeslice │ │ │ ├── uninstalling-kubeslice.mdx │ │ │ ├── deleting-the-slice.mdx │ │ │ └── deleting-the-project.mdx │ └── community.mdx ├── version-0.4.0 │ ├── release-notes │ │ ├── release-notes.mdx │ │ └── release-notes-for-kubeslice-oss-0.4.0.mdx │ ├── cloud-cluster-quick-start.mdx │ ├── reference │ │ └── reference.mdx │ ├── getting-started-with-cloud-clusters │ │ ├── uninstalling-kubeslice │ │ │ ├── deleting-the-slice.mdx │ │ │ └── deleting-the-project.mdx │ │ └── installing-kubeslice │ │ │ └── isolating-namespaces.mdx │ └── community.mdx ├── version-1.0.0 │ ├── get-started │ │ └── prerequisites │ │ │ ├── prerequisites-cluster-rbac-roles.mdx │ │ │ ├── prerequisites-cluster-networking.mdx │ │ │ ├── prerequisites-install-istio.mdx │ │ │ └── prerequisites-command-line-tools.mdx │ └── release-notes │ │ ├── release-notes-for-kubeslice-oss-0.5.1.mdx │ │ ├── release-notes-for-kubeslice-oss-0.4.0.mdx │ │ ├── release-notes-for-kubeslice-oss-0.6.0.mdx │ │ └── release-notes-for-kubeslice-oss-1.0.0.mdx ├── version-1.1.0 │ ├── get-started │ │ └── prerequisites │ │ │ ├── prerequisites-cluster-rbac-roles.mdx │ │ │ ├── prerequisites-cluster-networking.mdx │ │ │ ├── prerequisites-install-istio.mdx │ │ │ └── prerequisites-command-line-tools.mdx │ └── release-notes │ │ ├── release-notes-for-kubeslice-oss-0.5.1.mdx │ │ ├── release-notes-for-kubeslice-oss-0.4.0.mdx │ │ ├── release-notes-for-kubeslice-oss-0.6.0.mdx │ │ └── release-notes-for-kubeslice-oss-1.0.0.mdx ├── version-1.2.0 │ ├── get-started │ │ └── prerequisites │ │ │ ├── prerequisites-cluster-rbac-roles.mdx │ │ │ ├── prerequisites-cluster-networking.mdx │ │ │ ├── prerequisites-install-istio.mdx │ │ │ └── prerequisites-command-line-tools.mdx │ └── release-notes │ │ ├── release-notes-for-kubeslice-oss-0.5.1.mdx │ │ ├── release-notes-for-kubeslice-oss-0.4.0.mdx │ │ ├── release-notes-for-kubeslice-oss-1.2.1.mdx │ │ ├── release-notes-for-kubeslice-oss-1.2.0.mdx │ │ ├── release-notes-for-kubeslice-oss-0.6.0.mdx │ │ └── release-notes-for-kubeslice-oss-1.0.0.mdx ├── version-1.3.0 │ ├── get-started │ │ └── prerequisites │ │ │ ├── prerequisites-cluster-rbac-roles.mdx │ │ │ ├── prerequisites-cluster-networking.mdx │ │ │ ├── prerequisites-install-istio.mdx │ │ │ └── prerequisites-command-line-tools.mdx │ └── release-notes │ │ ├── release-notes-for-kubeslice-oss-1.3.1.mdx │ │ ├── release-notes-for-kubeslice-oss-0.5.1.mdx │ │ ├── release-notes-for-kubeslice-oss-1.3.0.mdx │ │ ├── release-notes-for-kubeslice-oss-1.3.1-cli.mdx │ │ ├── release-notes-for-kubeslice-oss-0.4.0.mdx │ │ ├── release-notes-for-kubeslice-oss-1.2.1.mdx │ │ ├── release-notes-for-kubeslice-oss-1.2.0.mdx │ │ ├── release-notes-for-kubeslice-oss-0.6.0.mdx │ │ └── release-notes-for-kubeslice-oss-1.0.0.mdx ├── version-1.4.0 │ ├── get-started │ │ └── prerequisites │ │ │ ├── prerequisites-cluster-rbac-roles.mdx │ │ │ ├── prerequisites-cluster-networking.mdx │ │ │ ├── prerequisites-install-istio.mdx │ │ │ └── prerequisites-command-line-tools.mdx │ └── release-notes │ │ ├── release-notes-for-kubeslice-oss-1.3.1.mdx │ │ ├── release-notes-for-kubeslice-oss-0.5.1.mdx │ │ ├── release-notes-for-kubeslice-oss-1.4.0.mdx │ │ ├── release-notes-for-kubeslice-oss-1.3.0.mdx │ │ ├── release-notes-for-kubeslice-oss-1.3.1-cli.mdx │ │ ├── release-notes-for-kubeslice-oss-0.4.0.mdx │ │ ├── release-notes-for-kubeslice-oss-1.2.1.mdx │ │ ├── release-notes-for-kubeslice-oss-1.2.0.mdx │ │ └── release-notes-for-kubeslice-oss-0.6.0.mdx ├── version-0.5.0 │ ├── reference │ │ └── reference.mdx │ ├── cloud-cluster-quick-start.mdx │ ├── release-notes │ │ ├── release-notes-for-kubeslice-oss-0.5.1.mdx │ │ └── release-notes-for-kubeslice-oss-0.4.0.mdx │ ├── getting-started-with-cloud-clusters │ │ ├── uninstalling-kubeslice │ │ │ ├── deleting-the-slice.mdx │ │ │ └── deleting-the-project.mdx │ │ └── installing-kubeslice │ │ │ └── isolating-namespaces.mdx │ └── community.mdx ├── version-0.6.0 │ ├── cloud-cluster-quick-start.mdx │ ├── reference │ │ └── reference.mdx │ ├── release-notes │ │ ├── release-notes-for-kubeslice-oss-0.5.1.mdx │ │ ├── release-notes-for-kubeslice-oss-0.4.0.mdx │ │ └── release-notes-for-kubeslice-oss-0.6.0.mdx │ ├── getting-started-with-cloud-clusters │ │ ├── uninstalling-kubeslice │ │ │ ├── deleting-the-slice.mdx │ │ │ └── deleting-the-project.mdx │ │ └── installing-kubeslice │ │ │ └── isolating-namespaces.mdx │ ├── features │ │ └── ipam.mdx │ └── community.mdx └── version-0.7.0 │ ├── cloud-cluster-quick-start.mdx │ ├── reference │ └── reference.mdx │ ├── release-notes │ ├── release-notes-for-kubeslice-oss-0.5.1.mdx │ ├── release-notes-for-kubeslice-oss-0.4.0.mdx │ └── release-notes-for-kubeslice-oss-0.6.0.mdx │ ├── getting-started-with-cloud-clusters │ ├── uninstalling-kubeslice │ │ ├── deleting-the-slice.mdx │ │ └── deleting-the-project.mdx │ └── installing-kubeslice │ │ └── isolating-namespaces.mdx │ ├── features │ └── ipam.mdx │ └── community.mdx ├── versions.json ├── docker-compose-prod.yaml ├── Dockerfile ├── prod.dockerfile ├── MAINTAINERS.md ├── .gitignore ├── docker-compose.yaml ├── spellcheck.yml ├── sidebars.js ├── utils.js ├── AUTHORS └── package.json /static/.nojekyll: -------------------------------------------------------------------------------- 1 | -------------------------------------------------------------------------------- /.dockerignore: -------------------------------------------------------------------------------- 1 | build 2 | .docusaurus 3 | node_modules 4 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/config.yml: -------------------------------------------------------------------------------- 1 | blank_issues_enabled: false 2 | -------------------------------------------------------------------------------- /static/img/avesha.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/static/img/avesha.png -------------------------------------------------------------------------------- /static/img/Architecture-OS.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/static/img/Architecture-OS.png -------------------------------------------------------------------------------- /static/img/Kindclusters-OS.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/static/img/Kindclusters-OS.png -------------------------------------------------------------------------------- /babel.config.js: -------------------------------------------------------------------------------- 1 | module.exports = { 2 | presets: [require.resolve('@docusaurus/core/lib/babel/preset')], 3 | }; 4 | -------------------------------------------------------------------------------- /static/font/CherryBomb-Regular.ttf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/static/font/CherryBomb-Regular.ttf -------------------------------------------------------------------------------- /static/img/Bookinfo-productpage-OS.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/static/img/Bookinfo-productpage-OS.png -------------------------------------------------------------------------------- /static/img/Namespace-Isolation-OS.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/static/img/Namespace-Isolation-OS.png -------------------------------------------------------------------------------- /static/img/community-register-free.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/static/img/community-register-free.png -------------------------------------------------------------------------------- /static/img/kubeslice-illustration.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/static/img/kubeslice-illustration.png -------------------------------------------------------------------------------- /images/images/kubeslice-cli/mac-download.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/kubeslice-cli/mac-download.png -------------------------------------------------------------------------------- /images/images/version1.0.0/monitor/add-to-slack.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.0.0/monitor/add-to-slack.png -------------------------------------------------------------------------------- /images/images/version1.1.0/monitor/add-to-slack.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.1.0/monitor/add-to-slack.png -------------------------------------------------------------------------------- /images/images/version1.2.0/monitor/add-to-slack.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.2.0/monitor/add-to-slack.png -------------------------------------------------------------------------------- /images/images/version1.3.0/monitor/add-to-slack.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.3.0/monitor/add-to-slack.png -------------------------------------------------------------------------------- /images/images/version-1.4.0/monitor/add-to-slack.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version-1.4.0/monitor/add-to-slack.png -------------------------------------------------------------------------------- /images/images/version-1.4.0/monitor/slack-webhook-save.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version-1.4.0/monitor/slack-webhook-save.png -------------------------------------------------------------------------------- /images/images/version1.0.0/monitor/slack-installed-apps.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.0.0/monitor/slack-installed-apps.png -------------------------------------------------------------------------------- /images/images/version1.0.0/monitor/slack-webhook-save.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.0.0/monitor/slack-webhook-save.png -------------------------------------------------------------------------------- /images/images/version1.0.0/monitoring-events/ksm-events.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.0.0/monitoring-events/ksm-events.png -------------------------------------------------------------------------------- /images/images/version1.1.0/monitor/slack-installed-apps.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.1.0/monitor/slack-installed-apps.png -------------------------------------------------------------------------------- /images/images/version1.1.0/monitor/slack-webhook-save.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.1.0/monitor/slack-webhook-save.png -------------------------------------------------------------------------------- /images/images/version1.1.0/monitoring-events/ksm-events.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.1.0/monitoring-events/ksm-events.png -------------------------------------------------------------------------------- /images/images/version1.2.0/monitor/slack-installed-apps.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.2.0/monitor/slack-installed-apps.png -------------------------------------------------------------------------------- /images/images/version1.2.0/monitor/slack-webhook-save.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.2.0/monitor/slack-webhook-save.png -------------------------------------------------------------------------------- /images/images/version1.2.0/monitoring-events/ksm-events.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.2.0/monitoring-events/ksm-events.png -------------------------------------------------------------------------------- /images/images/version1.3.0/monitor/slack-installed-apps.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.3.0/monitor/slack-installed-apps.png -------------------------------------------------------------------------------- /images/images/version1.3.0/monitor/slack-webhook-save.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.3.0/monitor/slack-webhook-save.png -------------------------------------------------------------------------------- /images/images/version1.3.0/monitoring-events/ksm-events.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.3.0/monitoring-events/ksm-events.png -------------------------------------------------------------------------------- /images/images/version-1.4.0/monitor/slack-installed-apps.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version-1.4.0/monitor/slack-installed-apps.png -------------------------------------------------------------------------------- /images/images/version-1.4.0/monitor/slack-post-to-channel.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version-1.4.0/monitor/slack-post-to-channel.png -------------------------------------------------------------------------------- /images/images/version-1.4.0/monitoring-events/ksm-events.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version-1.4.0/monitoring-events/ksm-events.png -------------------------------------------------------------------------------- /images/images/version1.0.0/monitor/slack-copy-webhook-url.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.0.0/monitor/slack-copy-webhook-url.png -------------------------------------------------------------------------------- /images/images/version1.0.0/monitor/slack-post-to-channel.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.0.0/monitor/slack-post-to-channel.png -------------------------------------------------------------------------------- /images/images/version1.1.0/monitor/slack-copy-webhook-url.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.1.0/monitor/slack-copy-webhook-url.png -------------------------------------------------------------------------------- /images/images/version1.1.0/monitor/slack-post-to-channel.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.1.0/monitor/slack-post-to-channel.png -------------------------------------------------------------------------------- /images/images/version1.2.0/monitor/slack-copy-webhook-url.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.2.0/monitor/slack-copy-webhook-url.png -------------------------------------------------------------------------------- /images/images/version1.2.0/monitor/slack-post-to-channel.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.2.0/monitor/slack-post-to-channel.png -------------------------------------------------------------------------------- /images/images/version1.3.0/monitor/slack-copy-webhook-url.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.3.0/monitor/slack-copy-webhook-url.png -------------------------------------------------------------------------------- /images/images/version1.3.0/monitor/slack-post-to-channel.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.3.0/monitor/slack-post-to-channel.png -------------------------------------------------------------------------------- /images/images/version-1.4.0/monitor/slack-copy-webhook-url.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version-1.4.0/monitor/slack-copy-webhook-url.png -------------------------------------------------------------------------------- /images/images/version1.0.0/monitoring-events/app-level-token.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.0.0/monitoring-events/app-level-token.png -------------------------------------------------------------------------------- /images/images/version1.0.0/monitoring-events/create-channel1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.0.0/monitoring-events/create-channel1.png -------------------------------------------------------------------------------- /images/images/version1.1.0/monitoring-events/app-level-token.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.1.0/monitoring-events/app-level-token.png -------------------------------------------------------------------------------- /images/images/version1.1.0/monitoring-events/create-channel1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.1.0/monitoring-events/create-channel1.png -------------------------------------------------------------------------------- /images/images/version1.2.0/monitoring-events/app-level-token.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.2.0/monitoring-events/app-level-token.png -------------------------------------------------------------------------------- /images/images/version1.2.0/monitoring-events/create-channel1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.2.0/monitoring-events/create-channel1.png -------------------------------------------------------------------------------- /images/images/version1.3.0/monitoring-events/app-level-token.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.3.0/monitoring-events/app-level-token.png -------------------------------------------------------------------------------- /images/images/version1.3.0/monitoring-events/create-channel1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.3.0/monitoring-events/create-channel1.png -------------------------------------------------------------------------------- /images/images/version-1.4.0/monitor/slack-channel-admin-option.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version-1.4.0/monitor/slack-channel-admin-option.png -------------------------------------------------------------------------------- /images/images/version-1.4.0/monitoring-events/app-level-token.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version-1.4.0/monitoring-events/app-level-token.png -------------------------------------------------------------------------------- /images/images/version-1.4.0/monitoring-events/create-channel1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version-1.4.0/monitoring-events/create-channel1.png -------------------------------------------------------------------------------- /images/images/version1.0.0/monitor/slack-channel-admin-option.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.0.0/monitor/slack-channel-admin-option.png -------------------------------------------------------------------------------- /images/images/version1.1.0/monitor/slack-channel-admin-option.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.1.0/monitor/slack-channel-admin-option.png -------------------------------------------------------------------------------- /images/images/version1.2.0/monitor/slack-channel-admin-option.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.2.0/monitor/slack-channel-admin-option.png -------------------------------------------------------------------------------- /images/images/version1.3.0/monitor/slack-channel-admin-option.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.3.0/monitor/slack-channel-admin-option.png -------------------------------------------------------------------------------- /src/theme/MDXComponents.js: -------------------------------------------------------------------------------- 1 | import React from 'react'; 2 | import MDXComponents from '@theme-original/MDXComponents'; 3 | 4 | export default { 5 | ...MDXComponents, 6 | }; 7 | -------------------------------------------------------------------------------- /images/images/version-1.4.0/monitoring-events/add-bot-to-channel.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version-1.4.0/monitoring-events/add-bot-to-channel.png -------------------------------------------------------------------------------- /images/images/version-1.4.0/monitoring-events/kubernetes-events1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version-1.4.0/monitoring-events/kubernetes-events1.png -------------------------------------------------------------------------------- /images/images/version-1.4.0/monitoring-events/kubernetes-events2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version-1.4.0/monitoring-events/kubernetes-events2.png -------------------------------------------------------------------------------- /images/images/version-1.4.0/monitoring-events/kubernetes-events3.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version-1.4.0/monitoring-events/kubernetes-events3.png -------------------------------------------------------------------------------- /images/images/version-1.4.0/monitoring-events/kubernetes-events4.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version-1.4.0/monitoring-events/kubernetes-events4.png -------------------------------------------------------------------------------- /images/images/version-1.4.0/monitoring-events/kubernetes-events5.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version-1.4.0/monitoring-events/kubernetes-events5.png -------------------------------------------------------------------------------- /images/images/version-1.4.0/use-cases/configure-mongodb/overview.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version-1.4.0/use-cases/configure-mongodb/overview.png -------------------------------------------------------------------------------- /images/images/version1.0.0/monitoring-events/add-bot-to-channel.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.0.0/monitoring-events/add-bot-to-channel.png -------------------------------------------------------------------------------- /images/images/version1.0.0/monitoring-events/bot-user-oauth-token.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.0.0/monitoring-events/bot-user-oauth-token.png -------------------------------------------------------------------------------- /images/images/version1.0.0/monitoring-events/botkube-app-in-slack.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.0.0/monitoring-events/botkube-app-in-slack.png -------------------------------------------------------------------------------- /images/images/version1.0.0/monitoring-events/copy-app-level-token.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.0.0/monitoring-events/copy-app-level-token.png -------------------------------------------------------------------------------- /images/images/version1.0.0/monitoring-events/kubernetes-events1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.0.0/monitoring-events/kubernetes-events1.png -------------------------------------------------------------------------------- /images/images/version1.0.0/monitoring-events/kubernetes-events2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.0.0/monitoring-events/kubernetes-events2.png -------------------------------------------------------------------------------- /images/images/version1.0.0/monitoring-events/kubernetes-events3.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.0.0/monitoring-events/kubernetes-events3.png -------------------------------------------------------------------------------- /images/images/version1.0.0/monitoring-events/kubernetes-events4.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.0.0/monitoring-events/kubernetes-events4.png -------------------------------------------------------------------------------- /images/images/version1.0.0/monitoring-events/kubernetes-events5.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.0.0/monitoring-events/kubernetes-events5.png -------------------------------------------------------------------------------- /images/images/version1.1.0/monitoring-events/add-bot-to-channel.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.1.0/monitoring-events/add-bot-to-channel.png -------------------------------------------------------------------------------- /images/images/version1.1.0/monitoring-events/bot-user-oauth-token.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.1.0/monitoring-events/bot-user-oauth-token.png -------------------------------------------------------------------------------- /images/images/version1.1.0/monitoring-events/botkube-app-in-slack.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.1.0/monitoring-events/botkube-app-in-slack.png -------------------------------------------------------------------------------- /images/images/version1.1.0/monitoring-events/copy-app-level-token.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.1.0/monitoring-events/copy-app-level-token.png -------------------------------------------------------------------------------- /images/images/version1.1.0/monitoring-events/kubernetes-events1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.1.0/monitoring-events/kubernetes-events1.png -------------------------------------------------------------------------------- /images/images/version1.1.0/monitoring-events/kubernetes-events2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.1.0/monitoring-events/kubernetes-events2.png -------------------------------------------------------------------------------- /images/images/version1.1.0/monitoring-events/kubernetes-events3.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.1.0/monitoring-events/kubernetes-events3.png -------------------------------------------------------------------------------- /images/images/version1.1.0/monitoring-events/kubernetes-events4.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.1.0/monitoring-events/kubernetes-events4.png -------------------------------------------------------------------------------- /images/images/version1.1.0/monitoring-events/kubernetes-events5.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.1.0/monitoring-events/kubernetes-events5.png -------------------------------------------------------------------------------- /images/images/version1.2.0/monitoring-events/add-bot-to-channel.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.2.0/monitoring-events/add-bot-to-channel.png -------------------------------------------------------------------------------- /images/images/version1.2.0/monitoring-events/bot-user-oauth-token.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.2.0/monitoring-events/bot-user-oauth-token.png -------------------------------------------------------------------------------- /images/images/version1.2.0/monitoring-events/botkube-app-in-slack.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.2.0/monitoring-events/botkube-app-in-slack.png -------------------------------------------------------------------------------- /images/images/version1.2.0/monitoring-events/copy-app-level-token.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.2.0/monitoring-events/copy-app-level-token.png -------------------------------------------------------------------------------- /images/images/version1.2.0/monitoring-events/kubernetes-events1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.2.0/monitoring-events/kubernetes-events1.png -------------------------------------------------------------------------------- /images/images/version1.2.0/monitoring-events/kubernetes-events2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.2.0/monitoring-events/kubernetes-events2.png -------------------------------------------------------------------------------- /images/images/version1.2.0/monitoring-events/kubernetes-events3.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.2.0/monitoring-events/kubernetes-events3.png -------------------------------------------------------------------------------- /images/images/version1.2.0/monitoring-events/kubernetes-events4.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.2.0/monitoring-events/kubernetes-events4.png -------------------------------------------------------------------------------- /images/images/version1.2.0/monitoring-events/kubernetes-events5.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.2.0/monitoring-events/kubernetes-events5.png -------------------------------------------------------------------------------- /images/images/version1.3.0/monitoring-events/add-bot-to-channel.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.3.0/monitoring-events/add-bot-to-channel.png -------------------------------------------------------------------------------- /images/images/version1.3.0/monitoring-events/bot-user-oauth-token.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.3.0/monitoring-events/bot-user-oauth-token.png -------------------------------------------------------------------------------- /images/images/version1.3.0/monitoring-events/botkube-app-in-slack.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.3.0/monitoring-events/botkube-app-in-slack.png -------------------------------------------------------------------------------- /images/images/version1.3.0/monitoring-events/copy-app-level-token.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.3.0/monitoring-events/copy-app-level-token.png -------------------------------------------------------------------------------- /images/images/version1.3.0/monitoring-events/kubernetes-events1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.3.0/monitoring-events/kubernetes-events1.png -------------------------------------------------------------------------------- /images/images/version1.3.0/monitoring-events/kubernetes-events2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.3.0/monitoring-events/kubernetes-events2.png -------------------------------------------------------------------------------- /images/images/version1.3.0/monitoring-events/kubernetes-events3.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.3.0/monitoring-events/kubernetes-events3.png -------------------------------------------------------------------------------- /images/images/version1.3.0/monitoring-events/kubernetes-events4.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.3.0/monitoring-events/kubernetes-events4.png -------------------------------------------------------------------------------- /images/images/version1.3.0/monitoring-events/kubernetes-events5.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.3.0/monitoring-events/kubernetes-events5.png -------------------------------------------------------------------------------- /images/images/version1.3.0/use-cases/configure-mongodb/overview.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.3.0/use-cases/configure-mongodb/overview.png -------------------------------------------------------------------------------- /src/theme/DocSidebar/index.d.ts: -------------------------------------------------------------------------------- 1 | /// 2 | import type { Props } from '@theme/DocSidebar'; 3 | export default function DocSidebar(props: Props): JSX.Element; 4 | -------------------------------------------------------------------------------- /versioned_docs/version-0.2.0/release-notes/release-notes.mdx: -------------------------------------------------------------------------------- 1 | # Release Notes 2 | This contains the release notes of KubeSlice arranged in the reverse chronological order of the version. -------------------------------------------------------------------------------- /versioned_docs/version-0.3.0/release-notes/release-notes.mdx: -------------------------------------------------------------------------------- 1 | # Release Notes 2 | This contains the release notes of KubeSlice arranged in the reverse chronological order of the version. -------------------------------------------------------------------------------- /versioned_docs/version-0.4.0/release-notes/release-notes.mdx: -------------------------------------------------------------------------------- 1 | # RELEASE NOTES 2 | This contains the release notes of KubeSlice arranged in the reverse chronological order of the version. -------------------------------------------------------------------------------- /images/images/version-1.4.0/monitoring-events/bot-user-oauth-token.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version-1.4.0/monitoring-events/bot-user-oauth-token.png -------------------------------------------------------------------------------- /images/images/version-1.4.0/monitoring-events/botkube-app-in-slack.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version-1.4.0/monitoring-events/botkube-app-in-slack.png -------------------------------------------------------------------------------- /images/images/version-1.4.0/monitoring-events/copy-app-level-token.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version-1.4.0/monitoring-events/copy-app-level-token.png -------------------------------------------------------------------------------- /images/images/version1.3.0/use-cases/configure-mongodb/host-mapping.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.3.0/use-cases/configure-mongodb/host-mapping.png -------------------------------------------------------------------------------- /images/images/version-1.4.0/key-features/support-for-private-clusters.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version-1.4.0/key-features/support-for-private-clusters.png -------------------------------------------------------------------------------- /images/images/version-1.4.0/monitoring-events/generate-app-level-token.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version-1.4.0/monitoring-events/generate-app-level-token.png -------------------------------------------------------------------------------- /images/images/version-1.4.0/monitoring-events/kubeslice-worker-events.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version-1.4.0/monitoring-events/kubeslice-worker-events.png -------------------------------------------------------------------------------- /images/images/version-1.4.0/use-cases/configure-mongodb/app-definition.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version-1.4.0/use-cases/configure-mongodb/app-definition.png -------------------------------------------------------------------------------- /images/images/version-1.4.0/use-cases/configure-mongodb/create-api-key.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version-1.4.0/use-cases/configure-mongodb/create-api-key.png -------------------------------------------------------------------------------- /images/images/version-1.4.0/use-cases/configure-mongodb/host-mapping.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version-1.4.0/use-cases/configure-mongodb/host-mapping.png -------------------------------------------------------------------------------- /images/images/version-1.4.0/use-cases/configure-mongodb/ops-deployment.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version-1.4.0/use-cases/configure-mongodb/ops-deployment.png -------------------------------------------------------------------------------- /images/images/version-1.4.0/use-cases/configure-mongodb/ops-manager-db.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version-1.4.0/use-cases/configure-mongodb/ops-manager-db.png -------------------------------------------------------------------------------- /images/images/version-1.4.0/use-cases/configure-mongodb/ops-manager-ui.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version-1.4.0/use-cases/configure-mongodb/ops-manager-ui.png -------------------------------------------------------------------------------- /images/images/version1.0.0/monitoring-events/generate-app-level-token.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.0.0/monitoring-events/generate-app-level-token.png -------------------------------------------------------------------------------- /images/images/version1.0.0/monitoring-events/kubeslice-worker-events.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.0.0/monitoring-events/kubeslice-worker-events.png -------------------------------------------------------------------------------- /images/images/version1.1.0/monitoring-events/generate-app-level-token.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.1.0/monitoring-events/generate-app-level-token.png -------------------------------------------------------------------------------- /images/images/version1.1.0/monitoring-events/kubeslice-worker-events.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.1.0/monitoring-events/kubeslice-worker-events.png -------------------------------------------------------------------------------- /images/images/version1.2.0/key-features/support-for-private-clusters.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.2.0/key-features/support-for-private-clusters.png -------------------------------------------------------------------------------- /images/images/version1.2.0/monitoring-events/generate-app-level-token.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.2.0/monitoring-events/generate-app-level-token.png -------------------------------------------------------------------------------- /images/images/version1.2.0/monitoring-events/kubeslice-worker-events.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.2.0/monitoring-events/kubeslice-worker-events.png -------------------------------------------------------------------------------- /images/images/version1.3.0/key-features/support-for-private-clusters.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.3.0/key-features/support-for-private-clusters.png -------------------------------------------------------------------------------- /images/images/version1.3.0/monitoring-events/generate-app-level-token.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.3.0/monitoring-events/generate-app-level-token.png -------------------------------------------------------------------------------- /images/images/version1.3.0/monitoring-events/kubeslice-worker-events.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.3.0/monitoring-events/kubeslice-worker-events.png -------------------------------------------------------------------------------- /images/images/version1.3.0/use-cases/configure-mongodb/api-access-list.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.3.0/use-cases/configure-mongodb/api-access-list.png -------------------------------------------------------------------------------- /images/images/version1.3.0/use-cases/configure-mongodb/app-definition.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.3.0/use-cases/configure-mongodb/app-definition.png -------------------------------------------------------------------------------- /images/images/version1.3.0/use-cases/configure-mongodb/create-api-key.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.3.0/use-cases/configure-mongodb/create-api-key.png -------------------------------------------------------------------------------- /images/images/version1.3.0/use-cases/configure-mongodb/ops-deployment.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.3.0/use-cases/configure-mongodb/ops-deployment.png -------------------------------------------------------------------------------- /images/images/version1.3.0/use-cases/configure-mongodb/ops-manager-db.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.3.0/use-cases/configure-mongodb/ops-manager-db.png -------------------------------------------------------------------------------- /images/images/version1.3.0/use-cases/configure-mongodb/ops-manager-ui.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.3.0/use-cases/configure-mongodb/ops-manager-ui.png -------------------------------------------------------------------------------- /images/images/version-1.4.0/use-cases/configure-mongodb/api-access-list.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version-1.4.0/use-cases/configure-mongodb/api-access-list.png -------------------------------------------------------------------------------- /images/images/version1.0.0/monitoring-events/kubeslice-controller-events.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.0.0/monitoring-events/kubeslice-controller-events.png -------------------------------------------------------------------------------- /images/images/version1.1.0/monitoring-events/kubeslice-controller-events.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.1.0/monitoring-events/kubeslice-controller-events.png -------------------------------------------------------------------------------- /images/images/version1.2.0/monitoring-events/kubeslice-controller-events.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.2.0/monitoring-events/kubeslice-controller-events.png -------------------------------------------------------------------------------- /images/images/version1.3.0/monitoring-events/kubeslice-controller-events.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.3.0/monitoring-events/kubeslice-controller-events.png -------------------------------------------------------------------------------- /images/images/version1.3.0/use-cases/configure-mongodb/ops-organizations.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.3.0/use-cases/configure-mongodb/ops-organizations.png -------------------------------------------------------------------------------- /images/images/version1.3.0/use-cases/configure-mongodb/save-api-key-info.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.3.0/use-cases/configure-mongodb/save-api-key-info.png -------------------------------------------------------------------------------- /versions.json: -------------------------------------------------------------------------------- 1 | [ 2 | "1.4.0", 3 | "1.3.0", 4 | "1.2.0", 5 | "1.1.0", 6 | "1.0.0", 7 | "0.7.0", 8 | "0.6.0", 9 | "0.5.0", 10 | "0.4.0", 11 | "0.3.0", 12 | "0.2.0" 13 | ] 14 | -------------------------------------------------------------------------------- /images/images/version-1.4.0/monitor/slack-add-incoming-webhook-integration.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version-1.4.0/monitor/slack-add-incoming-webhook-integration.png -------------------------------------------------------------------------------- /images/images/version-1.4.0/monitoring-events/kubeslice-controller-events.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version-1.4.0/monitoring-events/kubeslice-controller-events.png -------------------------------------------------------------------------------- /images/images/version-1.4.0/use-cases/configure-mongodb/ops-access-manager.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version-1.4.0/use-cases/configure-mongodb/ops-access-manager.png -------------------------------------------------------------------------------- /images/images/version-1.4.0/use-cases/configure-mongodb/ops-organizations.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version-1.4.0/use-cases/configure-mongodb/ops-organizations.png -------------------------------------------------------------------------------- /images/images/version-1.4.0/use-cases/configure-mongodb/save-api-key-info.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version-1.4.0/use-cases/configure-mongodb/save-api-key-info.png -------------------------------------------------------------------------------- /images/images/version1.0.0/monitor/slack-add-incoming-webhook-integration.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.0.0/monitor/slack-add-incoming-webhook-integration.png -------------------------------------------------------------------------------- /images/images/version1.1.0/monitor/slack-add-incoming-webhook-integration.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.1.0/monitor/slack-add-incoming-webhook-integration.png -------------------------------------------------------------------------------- /images/images/version1.2.0/monitor/slack-add-incoming-webhook-integration.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.2.0/monitor/slack-add-incoming-webhook-integration.png -------------------------------------------------------------------------------- /images/images/version1.3.0/monitor/slack-add-incoming-webhook-integration.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.3.0/monitor/slack-add-incoming-webhook-integration.png -------------------------------------------------------------------------------- /images/images/version1.3.0/use-cases/configure-mongodb/ops-access-manager.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.3.0/use-cases/configure-mongodb/ops-access-manager.png -------------------------------------------------------------------------------- /src/theme/Footer/index.d.ts: -------------------------------------------------------------------------------- 1 | import React from 'react'; 2 | declare function Footer(): JSX.Element | null; 3 | declare const _default: React.MemoExoticComponent; 4 | export default _default; 5 | -------------------------------------------------------------------------------- /docker-compose-prod.yaml: -------------------------------------------------------------------------------- 1 | version: "3" 2 | services: 3 | oss: 4 | build: 5 | context: . 6 | dockerfile: prod.dockerfile 7 | restart: always 8 | ports: 9 | - "3000:3000" 10 | -------------------------------------------------------------------------------- /images/images/version-1.4.0/use-cases/configure-mongodb/add-access-list-entry.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version-1.4.0/use-cases/configure-mongodb/add-access-list-entry.png -------------------------------------------------------------------------------- /images/images/version-1.4.0/use-cases/configure-mongodb/organization-settings.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version-1.4.0/use-cases/configure-mongodb/organization-settings.png -------------------------------------------------------------------------------- /images/images/version-1.4.0/use-cases/configure-mongodb/replicaset-deployment.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version-1.4.0/use-cases/configure-mongodb/replicaset-deployment.png -------------------------------------------------------------------------------- /images/images/version1.3.0/use-cases/configure-mongodb/add-access-list-entry.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.3.0/use-cases/configure-mongodb/add-access-list-entry.png -------------------------------------------------------------------------------- /images/images/version1.3.0/use-cases/configure-mongodb/organization-settings.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.3.0/use-cases/configure-mongodb/organization-settings.png -------------------------------------------------------------------------------- /images/images/version1.3.0/use-cases/configure-mongodb/replicaset-deployment.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.3.0/use-cases/configure-mongodb/replicaset-deployment.png -------------------------------------------------------------------------------- /images/images/version-1.4.0/use-cases/configure-mongodb/replicaset-within-clusters.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version-1.4.0/use-cases/configure-mongodb/replicaset-within-clusters.png -------------------------------------------------------------------------------- /images/images/version1.3.0/use-cases/configure-mongodb/replicaset-outside-clusters.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.3.0/use-cases/configure-mongodb/replicaset-outside-clusters.png -------------------------------------------------------------------------------- /images/images/version1.3.0/use-cases/configure-mongodb/replicaset-within-clusters.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version1.3.0/use-cases/configure-mongodb/replicaset-within-clusters.png -------------------------------------------------------------------------------- /src/theme/DocVersionBanner/index.d.ts: -------------------------------------------------------------------------------- 1 | /// 2 | import type { Props } from '@theme/DocVersionBanner'; 3 | export default function DocVersionBanner({ className, }: Props): JSX.Element | null; 4 | -------------------------------------------------------------------------------- /Dockerfile: -------------------------------------------------------------------------------- 1 | FROM node:18.20.4-alpine as builder 2 | WORKDIR /build 3 | COPY . ./ 4 | COPY ./images/ ./static/images 5 | RUN npm install 6 | 7 | EXPOSE 3000 8 | ENTRYPOINT ["npm", "run"] 9 | CMD ["start:docker"] 10 | -------------------------------------------------------------------------------- /images/images/version-1.4.0/use-cases/configure-mongodb/replicaset-outside-clusters.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kubeslice/docs/HEAD/images/images/version-1.4.0/use-cases/configure-mongodb/replicaset-outside-clusters.png -------------------------------------------------------------------------------- /versioned_docs/version-0.3.0/getting-started-with-cloud-clusters/tutorials/tutorials.mdx: -------------------------------------------------------------------------------- 1 | # Tutorials 2 | The tutorials on the following applications helps you in getting started with KubeSlice: 3 | 4 | * iPerf 5 | * BookInfo -------------------------------------------------------------------------------- /versioned_docs/version-0.2.0/getting-started-with-cloud-clusters/tutorials/tutorials.mdx: -------------------------------------------------------------------------------- 1 | # Tutorials 2 | The tutorials on the following applications helps you in getting started with KubeSlice: 3 | 4 | * iPerf 5 | * BookInfo 6 | -------------------------------------------------------------------------------- /prod.dockerfile: -------------------------------------------------------------------------------- 1 | FROM node:18.2.0-alpine as builder 2 | WORKDIR /build 3 | COPY package.json ./ 4 | COPY package-lock.json ./ 5 | RUN npm install 6 | COPY . ./ 7 | RUN npm run build 8 | 9 | EXPOSE 3000 10 | ENTRYPOINT ["npm", "run"] 11 | CMD ["serve"] 12 | -------------------------------------------------------------------------------- /MAINTAINERS.md: -------------------------------------------------------------------------------- 1 | # KubeSlice Controller Maintainers 2 | The maintainers are generally available in Slack at https://kubernetes.slack.com in channel #kubeslice 3 | 4 | Veena M J veena@avesha.io 5 | Uma T uma.thammanagoudr@avesha.io 6 | Eric Peterson eric@avesha.io 7 | Md Imran imran@avesha.io 8 | Priyank Upadhyay priyank@avesha.io 9 | -------------------------------------------------------------------------------- /src/theme/DocSidebar/Desktop/index.d.ts: -------------------------------------------------------------------------------- 1 | import React from 'react'; 2 | import type { Props } from '@theme/DocSidebar/Desktop'; 3 | declare function DocSidebarDesktop({ path, sidebar, onCollapse, isHidden }: Props): JSX.Element; 4 | declare const _default: React.MemoExoticComponent; 5 | export default _default; 6 | -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | # Dependencies 2 | /node_modules 3 | 4 | # Production 5 | /build 6 | 7 | # Generated files 8 | .docusaurus 9 | .cache-loader 10 | 11 | # Misc 12 | .DS_Store 13 | .env.local 14 | .env.development.local 15 | .env.test.local 16 | .env.production.local 17 | 18 | npm-debug.log* 19 | yarn-debug.log* 20 | yarn-error.log* 21 | 22 | # ide 23 | .idea 24 | *.iml 25 | -------------------------------------------------------------------------------- /docker-compose.yaml: -------------------------------------------------------------------------------- 1 | version: "3" 2 | services: 3 | oss: 4 | build: 5 | context: . 6 | dockerfile: Dockerfile 7 | restart: always 8 | ports: 9 | - "3000:3000" 10 | volumes: 11 | - ./versioned_docs:/build/versioned_docs 12 | - ./versioned_sidebars:/build/versioned_sidebars 13 | - ./versions.json:/build/versions.json 14 | - ./images:/build/static/images -------------------------------------------------------------------------------- /versioned_docs/version-1.0.0/get-started/prerequisites/prerequisites-cluster-rbac-roles.mdx: -------------------------------------------------------------------------------- 1 | # Required Cluster Roles (RBAC) 2 | Installing the KubeSlice Controller and Slice Operator **requires admin privileges** on the 3 | Kubernetes cluster. Therefore, only a user with the Kubernetes cluster admin role can 4 | perform this task. The correct name of the RBAC role for admin privileges in Kubernetes is 5 | `cluster-admin`. -------------------------------------------------------------------------------- /versioned_docs/version-1.1.0/get-started/prerequisites/prerequisites-cluster-rbac-roles.mdx: -------------------------------------------------------------------------------- 1 | # Required Cluster Roles (RBAC) 2 | Installing the KubeSlice Controller and Slice Operator **requires admin privileges** on the 3 | Kubernetes cluster. Therefore, only a user with the Kubernetes cluster admin role can 4 | perform this task. The correct name of the RBAC role for admin privileges in Kubernetes is 5 | `cluster-admin`. -------------------------------------------------------------------------------- /versioned_docs/version-1.2.0/get-started/prerequisites/prerequisites-cluster-rbac-roles.mdx: -------------------------------------------------------------------------------- 1 | # Required Cluster Roles (RBAC) 2 | Installing the KubeSlice Controller and Slice Operator **requires admin privileges** on the 3 | Kubernetes cluster. Therefore, only a user with the Kubernetes cluster admin role can 4 | perform this task. The correct name of the RBAC role for admin privileges in Kubernetes is 5 | `cluster-admin`. -------------------------------------------------------------------------------- /versioned_docs/version-1.3.0/get-started/prerequisites/prerequisites-cluster-rbac-roles.mdx: -------------------------------------------------------------------------------- 1 | # Required Cluster Roles (RBAC) 2 | Installing the KubeSlice Controller and Slice Operator **requires admin privileges** on the 3 | Kubernetes cluster. Therefore, only a user with the Kubernetes cluster admin role can 4 | perform this task. The correct name of the RBAC role for admin privileges in Kubernetes is 5 | `cluster-admin`. -------------------------------------------------------------------------------- /versioned_docs/version-1.4.0/get-started/prerequisites/prerequisites-cluster-rbac-roles.mdx: -------------------------------------------------------------------------------- 1 | # Required Cluster Roles (RBAC) 2 | Installing the KubeSlice Controller and Slice Operator **requires admin privileges** on the 3 | Kubernetes cluster. Therefore, only a user with the Kubernetes cluster admin role can 4 | perform this task. The correct name of the RBAC role for admin privileges in Kubernetes is 5 | `cluster-admin`. -------------------------------------------------------------------------------- /static/img/x.svg: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | -------------------------------------------------------------------------------- /versioned_docs/version-0.2.0/getting-started-with-cloud-clusters/getting-started-with-cloud-clusters.mdx: -------------------------------------------------------------------------------- 1 | # Getting Started with Cloud Clusters 2 | 3 | This guide will help you to successfully register your clusters with the KubeSlice Controller and create a 4 | slice across the clusters. We have worked to make this experience as seamless as possible. 5 | If you have any comments, questions, or issues, please feel free to join our [community](/versioned_docs/version-0.2.0/community.mdx). 6 | -------------------------------------------------------------------------------- /versioned_docs/version-0.3.0/getting-started-with-cloud-clusters/getting-started-with-cloud-clusters.mdx: -------------------------------------------------------------------------------- 1 | # Getting Started with Cloud Clusters 2 | 3 | This guide will help you to successfully register your clusters with the KubeSlice Controller and create a 4 | slice across the clusters. We have worked to make this experience as seamless as possible. 5 | If you have any comments, questions, or issues, please feel free to join our [community](/versioned_docs/version-0.3.0/community.mdx). 6 | -------------------------------------------------------------------------------- /versioned_docs/version-0.2.0/getting-started-with-cloud-clusters/installing-kubeslice/installing-kubeslice.mdx: -------------------------------------------------------------------------------- 1 | # Installing KubeSlice 2 | 3 | ## Introduction 4 | 5 | There are the five main steps for installing the KubeSlice: 6 | 7 | 1. Installing the KubeSlice Controller 8 | 2. Creating the project 9 | 3. Registering the worker clusters 10 | 4. Creating the slices 11 | 5. Onboarding namespaces onto the slices 12 | 13 | This topic describes the steps to install your first KubeSlice. -------------------------------------------------------------------------------- /versioned_docs/version-0.3.0/getting-started-with-cloud-clusters/installing-kubeslice/installing-kubeslice.mdx: -------------------------------------------------------------------------------- 1 | # Installing KubeSlice 2 | 3 | ## Introduction 4 | 5 | There are the five main steps for installing the KubeSlice: 6 | 7 | 1. Installing the KubeSlice Controller 8 | 2. Creating the project 9 | 3. Registering the worker clusters 10 | 4. Creating the slices 11 | 5. Onboarding namespaces onto the slices 12 | 13 | This topic describes the steps to install your first KubeSlice. -------------------------------------------------------------------------------- /src/pages/index.module.css: -------------------------------------------------------------------------------- 1 | /** 2 | * CSS files with the .module.css suffix will be treated as CSS modules 3 | * and scoped locally. 4 | */ 5 | 6 | .heroBanner { 7 | padding: 4rem 0; 8 | text-align: center; 9 | position: relative; 10 | overflow: hidden; 11 | } 12 | 13 | @media screen and (max-width: 996px) { 14 | .heroBanner { 15 | padding: 2rem; 16 | } 17 | } 18 | 19 | .buttons { 20 | display: flex; 21 | align-items: center; 22 | justify-content: center; 23 | } 24 | -------------------------------------------------------------------------------- /spellcheck.yml: -------------------------------------------------------------------------------- 1 | matrix: 2 | - name: Markdown 3 | sources: 4 | - '**/*.mdx' 5 | - 'docs/versioned_docs/version-1.2.0/*.mdx' 6 | default_encoding: utf-8 7 | aspell: 8 | lang: en 9 | ignore-case: true 10 | dictionary: 11 | wordlists: 12 | - wordlist.txt 13 | encoding: utf-8 14 | pipeline: 15 | - pyspelling.filters.markdown: 16 | markdown_extensions: 17 | - pymdownx.superfences 18 | - pyspelling.filters.html: 19 | comments: false 20 | ignores: 21 | - code 22 | - pre -------------------------------------------------------------------------------- /src/pages/index.js: -------------------------------------------------------------------------------- 1 | import React from 'react'; 2 | import {Redirect} from '@docusaurus/router'; 3 | import useDocusaurusContext from '@docusaurus/useDocusaurusContext'; 4 | import NotFound from '@theme/NotFound'; 5 | 6 | export default function Home() { 7 | const { globalData } = useDocusaurusContext(); 8 | 9 | const versions = globalData['docusaurus-plugin-content-docs']['default']['versions']; 10 | const latestVersion = versions.filter(version => { 11 | if (version.isLast) 12 | return version; 13 | }) 14 | const path = latestVersion[0]?.path ; 15 | 16 | return path ? : 17 | } 18 | -------------------------------------------------------------------------------- /versioned_docs/version-0.2.0/getting-started-with-cloud-clusters/uninstalling-kubeslice/uninstalling-kubeslice.mdx: -------------------------------------------------------------------------------- 1 | # Uninstalling KubeSlice 2 | 3 | Introduction 4 | This topic describes the steps to uninstall the KubeSlice. To uninstall the KubeSlice 5 | Controller, follow these steps: 6 | 7 | * Offboard all namespaces from the slice 8 | * Delete the slice 9 | * Deregister your worker cluster 10 | * Delete the project 11 | * Uninstall the KubeSlice Controller 12 | 13 | :::info 14 | The order of operations in uninstalling the KubeSlice Controller is important to ensure 15 | all resources are cleaned up properly. Follow the order of operations provided under 16 | this topic. 17 | ::: 18 | -------------------------------------------------------------------------------- /versioned_docs/version-0.3.0/getting-started-with-cloud-clusters/uninstalling-kubeslice/uninstalling-kubeslice.mdx: -------------------------------------------------------------------------------- 1 | # Uninstalling KubeSlice 2 | 3 | Introduction 4 | This topic describes the steps to uninstall the KubeSlice. To uninstall the KubeSlice 5 | Controller, follow these steps: 6 | 7 | * Offboard all namespaces from the slice 8 | * Delete the slice 9 | * Deregister your worker cluster 10 | * Delete the project 11 | * Uninstall the KubeSlice Controller 12 | 13 | :::info 14 | The order of operations in uninstalling the KubeSlice Controller is important to ensure 15 | all resources are cleaned up properly. Follow the order of operations provided under 16 | this topic. 17 | ::: 18 | -------------------------------------------------------------------------------- /versioned_docs/version-0.4.0/cloud-cluster-quick-start.mdx: -------------------------------------------------------------------------------- 1 | # Cloud Clusters 2 | KubeSlice is a platform that offers an easy and rapid way to isolate and segment your 3 | applications within and across Kubernetes clusters. 4 | 5 | ![alt](/img/kubeslice-illustration.png) 6 | 7 | Use [kubeslice-cli](/versioned_docs/version-0.4.0/kubeslice-cli/getting-started.mdx) 8 | to quickly install KubeSlice on cloud clusters. For instructions, 9 | follow this [demo tutorial](versioned_docs/version-0.4.0/tutorials/kubeslice-cli-demo-on-cloud-clusters.mdx). 10 | This tutorial helps you to register your clusters with the KubeSlice Controller and create a 11 | slice across the clusters. We have worked to make this experience as seamless as possible. -------------------------------------------------------------------------------- /versioned_docs/version-1.3.0/release-notes/release-notes-for-kubeslice-oss-1.3.1.mdx: -------------------------------------------------------------------------------- 1 | # Release Notes for KubeSlice OSS 1.3.1 2 | 3 | *Release date: 28th May 2024* 4 | 5 | KubeSlice is a ***cloud-independent*** platform that combines network, application, Kubernetes, and deployment services 6 | in a framework to accelerate application deployment in a multi-cluster and multi-tenant environment. KubeSlice achieves this 7 | by creating logical application ***slice*** boundaries that enable seamless communication between pods and services across 8 | clusters, clouds, edges, and data centers. 9 | 10 | We continue to add new features and enhancements to KubeSlice. 11 | 12 | ## What's New :speaker: 13 | 14 | * We have made security vulnerability fixes. -------------------------------------------------------------------------------- /versioned_docs/version-1.4.0/release-notes/release-notes-for-kubeslice-oss-1.3.1.mdx: -------------------------------------------------------------------------------- 1 | # Release Notes for KubeSlice OSS 1.3.1 2 | 3 | *Release date: 28th May 2024* 4 | 5 | KubeSlice is a ***cloud-independent*** platform that combines network, application, Kubernetes, and deployment services 6 | in a framework to accelerate application deployment in a multi-cluster and multi-tenant environment. KubeSlice achieves this 7 | by creating logical application ***slice*** boundaries that enable seamless communication between pods and services across 8 | clusters, clouds, edges, and data centers. 9 | 10 | We continue to add new features and enhancements to KubeSlice. 11 | 12 | ## What's New :speaker: 13 | 14 | * We have made security vulnerability fixes. -------------------------------------------------------------------------------- /.github/workflows/spellcheck.yml: -------------------------------------------------------------------------------- 1 | name: Spellcheck Action 2 | on: 3 | pull_request: 4 | branches: [ "master" ] 5 | push: 6 | branches: [ "master" ] 7 | workflow_dispatch: 8 | jobs: 9 | build: 10 | name: Spellcheck 11 | runs-on: ubuntu-latest 12 | steps: 13 | # The checkout step 14 | - uses: actions/checkout@v3 15 | - uses: rojopolis/spellcheck-github-actions@0.36.0 16 | name: Spellcheck 17 | with: 18 | config_path: spellcheck.yml # put path to configuration file here 19 | output_file: spellcheck-output.txt 20 | - uses: actions/upload-artifact@v3 21 | if: '!cancelled()' # Do not upload artifact if job was cancelled 22 | with: 23 | name: Spellcheck Output 24 | path: spellcheck-output.txt -------------------------------------------------------------------------------- /versioned_docs/version-0.4.0/reference/reference.mdx: -------------------------------------------------------------------------------- 1 | # REFERENCE 2 | This section contains KubeSlice and kubeslice-cli reference documents. 3 | 4 | ## Configuration Guide 5 | - [Configuration Parameters](/versioned_docs/version-0.4.0/reference/configuration-parameters.mdx) 6 | - [kubeslice-cli Configuration Parameters](/versioned_docs/version-0.4.0/reference/kubeslice-cli-configuration-parameters.mdx) 7 | 8 | ## Customized Script 9 | - [Getting the Worker Secrets from the Controller](/versioned_docs/version-0.4.0/reference/script-to-get-the-secrets-of-the-worker-cluster.mdx) 10 | 11 | ## Topology Configuration 12 | - [Topology Template](/versioned_docs/version-0.4.0/reference/topology-template.mdx) 13 | - [Sample Configuration File](/versioned_docs/version-0.4.0/reference/sample-configuration-file.mdx) -------------------------------------------------------------------------------- /versioned_docs/version-0.5.0/reference/reference.mdx: -------------------------------------------------------------------------------- 1 | # REFERENCE 2 | This section contains KubeSlice and kubeslice-cli reference documents. 3 | 4 | ## Configuration Guide 5 | - [Configuration Parameters](/versioned_docs/version-0.5.0/reference/configuration-parameters.mdx) 6 | - [kubeslice-cli Configuration Parameters](/versioned_docs/version-0.5.0/reference/kubeslice-cli-configuration-parameters.mdx) 7 | 8 | ## Customized Script 9 | - [Getting the Worker Secrets from the Controller](/versioned_docs/version-0.5.0/reference/script-to-get-the-secrets-of-the-worker-cluster.mdx) 10 | 11 | ## Topology Configuration 12 | - [Topology Template](/versioned_docs/version-0.5.0/reference/topology-template.mdx) 13 | - [Sample Configuration File](/versioned_docs/version-0.5.0/reference/sample-configuration-file.mdx) -------------------------------------------------------------------------------- /versioned_docs/version-0.6.0/cloud-cluster-quick-start.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | sidebar_position: 1 3 | slug: / 4 | --- 5 | 6 | # Cloud Clusters 7 | --- 8 | 9 | KubeSlice is a platform that offers an easy and rapid way to isolate and segment your 10 | applications within and across Kubernetes clusters. 11 | 12 | ![alt](/img/kubeslice-illustration.png) 13 | Use [kubeslice-cli](/versioned_docs/version-0.6.0/kubeslice-cli/getting-started.mdx) 14 | to quickly install KubeSlice on cloud clusters. For instructions, 15 | follow this [demo tutorial](versioned_docs/version-0.6.0/tutorials/kubeslice-cli-demo-on-cloud-clusters.mdx). 16 | This tutorial helps you to register your clusters with the KubeSlice Controller and create a 17 | slice across the clusters. We have worked to make this experience as seamless as possible. -------------------------------------------------------------------------------- /versioned_docs/version-0.6.0/reference/reference.mdx: -------------------------------------------------------------------------------- 1 | # REFERENCE 2 | This section contains KubeSlice and kubeslice-cli reference documents. 3 | 4 | ## Configuration Guide 5 | - [Configuration Parameters](/versioned_docs/version-0.6.0/reference/configuration-parameters.mdx) 6 | - [kubeslice-cli Configuration Parameters](/versioned_docs/version-0.6.0/reference/kubeslice-cli-configuration-parameters.mdx) 7 | 8 | ## Customized Script 9 | - [Getting the Worker Secrets from the Controller](/versioned_docs/version-0.6.0/reference/script-to-get-the-secrets-of-the-worker-cluster.mdx) 10 | 11 | ## Topology Configuration 12 | - [Topology Template](/versioned_docs/version-0.6.0/reference/topology-template.mdx) 13 | - [Sample Configuration File](/versioned_docs/version-0.6.0/reference/sample-configuration-file.mdx) -------------------------------------------------------------------------------- /versioned_docs/version-0.7.0/cloud-cluster-quick-start.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | sidebar_position: 1 3 | slug: / 4 | --- 5 | 6 | # Cloud Clusters 7 | --- 8 | 9 | KubeSlice is a platform that offers an easy and rapid way to isolate and segment your 10 | applications within and across Kubernetes clusters. 11 | 12 | ![alt](/img/kubeslice-illustration.png) 13 | Use [kubeslice-cli](/versioned_docs/version-0.7.0/kubeslice-cli/getting-started.mdx) 14 | to quickly install KubeSlice on cloud clusters. For instructions, 15 | follow this [demo tutorial](versioned_docs/version-0.7.0/tutorials/kubeslice-cli-demo-on-cloud-clusters.mdx). 16 | This tutorial helps you to register your clusters with the KubeSlice Controller and create a 17 | slice across the clusters. We have worked to make this experience as seamless as possible. -------------------------------------------------------------------------------- /versioned_docs/version-0.7.0/reference/reference.mdx: -------------------------------------------------------------------------------- 1 | # REFERENCE 2 | This section contains KubeSlice and kubeslice-cli reference documents. 3 | 4 | ## Configuration Guide 5 | - [Configuration Parameters](/versioned_docs/version-0.7.0/reference/configuration-parameters.mdx) 6 | - [kubeslice-cli Configuration Parameters](/versioned_docs/version-0.7.0/reference/kubeslice-cli-configuration-parameters.mdx) 7 | 8 | ## Customized Script 9 | - [Getting the Worker Secrets from the Controller](/versioned_docs/version-0.7.0/reference/script-to-get-the-secrets-of-the-worker-cluster.mdx) 10 | 11 | ## Topology Configuration 12 | - [Topology Template](/versioned_docs/version-0.7.0/reference/topology-template.mdx) 13 | - [Sample Configuration File](/versioned_docs/version-0.7.0/reference/sample-configuration-file.mdx) -------------------------------------------------------------------------------- /versioned_docs/version-0.5.0/cloud-cluster-quick-start.mdx: -------------------------------------------------------------------------------- 1 | --- 2 | sidebar_position: 1 3 | slug: / 4 | --- 5 | 6 | # Cloud Clusters 7 | --- 8 | 9 | KubeSlice is a platform that offers an easy and rapid way to isolate and segment your 10 | applications within and across Kubernetes clusters. 11 | 12 | ![alt](/img/kubeslice-illustration.png) 13 | 14 | Use [kubeslice-cli](/versioned_docs/version-0.5.0/kubeslice-cli/getting-started.mdx) 15 | to quickly install KubeSlice on cloud clusters. For instructions, 16 | follow this [demo tutorial](versioned_docs/version-0.5.0/tutorials/kubeslice-cli-demo-on-cloud-clusters.mdx). 17 | This tutorial helps you to register your clusters with the KubeSlice Controller and create a 18 | slice across the clusters. We have worked to make this experience as seamless as possible. 19 | -------------------------------------------------------------------------------- /static/img/youtube.svg: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | -------------------------------------------------------------------------------- /src/theme/DocSidebar/index.js: -------------------------------------------------------------------------------- 1 | import React from 'react'; 2 | import {useWindowSize} from '@docusaurus/theme-common'; 3 | import DocSidebarDesktop from '@theme/DocSidebar/Desktop'; 4 | import DocSidebarMobile from '@theme/DocSidebar/Mobile'; 5 | export default function DocSidebar(props) { 6 | const windowSize = useWindowSize(); 7 | // Desktop sidebar visible on hydration: need SSR rendering 8 | const shouldRenderSidebarDesktop = 9 | windowSize === 'desktop' || windowSize === 'ssr'; 10 | // Mobile sidebar not visible on hydration: can avoid SSR rendering 11 | const shouldRenderSidebarMobile = windowSize === 'mobile'; 12 | return ( 13 | <> 14 | {shouldRenderSidebarDesktop && } 15 | {shouldRenderSidebarMobile && } 16 | 17 | ); 18 | } 19 | -------------------------------------------------------------------------------- /static/img/linked-in.svg: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | -------------------------------------------------------------------------------- /sidebars.js: -------------------------------------------------------------------------------- 1 | /** 2 | * Creating a sidebar enables you to: 3 | - create an ordered group of docs 4 | - render a sidebar for each doc of that group 5 | - provide next/previous navigation 6 | 7 | The sidebars can be generated from the filesystem, or explicitly defined here. 8 | 9 | Create as many sidebars as you want. 10 | */ 11 | 12 | // @ts-check 13 | 14 | /** @type {import('@docusaurus/plugin-content-docs').SidebarsConfig} */ 15 | const sidebars = { 16 | // By default, Docusaurus generates a sidebar from the docs folder structure 17 | tutorialSidebar: [{type: 'autogenerated', dirName: '.'}], 18 | 19 | // But you can create a sidebar manually 20 | /* 21 | tutorialSidebar: [ 22 | { 23 | type: 'category', 24 | label: 'Tutorial', 25 | items: ['hello'], 26 | }, 27 | ], 28 | */ 29 | }; 30 | 31 | module.exports = sidebars; 32 | -------------------------------------------------------------------------------- /utils.js: -------------------------------------------------------------------------------- 1 | function uniquePath(path) { 2 | const segments = path?.split("/").filter(Boolean); 3 | for (let i = 0; i < segments.length; i++) { 4 | if (segments.length === 2 && segments[i] === segments[i + 1]) { 5 | return segments[0] + "/"; 6 | } 7 | } 8 | return path; 9 | } 10 | 11 | 12 | export function getValidPaths(items) { 13 | return items?.flatMap((item) => { 14 | const paths = []; 15 | 16 | if (item?.label) { 17 | if (item.label !== "Overview") { 18 | const formattedTitle = `category/${item?.label.toLowerCase().replace(/\s+/g, "-")}`; 19 | paths.push(formattedTitle); 20 | } 21 | } 22 | 23 | if (item?.items) { 24 | paths.push(...getValidPaths(item?.items)); 25 | } else if (typeof item === "string") { 26 | paths.push(uniquePath(item)); 27 | } 28 | 29 | return paths; 30 | }); 31 | } 32 | -------------------------------------------------------------------------------- /versioned_docs/version-0.5.0/release-notes/release-notes-for-kubeslice-oss-0.5.1.mdx: -------------------------------------------------------------------------------- 1 | # Release Notes for KubeSlice OSS 0.5.0 v1 2 | 3 | *Release date: 06 Jan 2023* 4 | 5 | KubeSlice is a ***cloud-independent*** platform that combines network, application, Kubernetes, and deployment services 6 | in a framework to accelerate application deployment in a multi-cluster and multi-tenant environment. KubeSlice achieves this 7 | by creating logical application ***slice*** boundaries that enable seamless communication between pods and services across 8 | clusters, clouds, edges, and data centers. 9 | 10 | We continue to add new features and enhancements to KubeSlice. 11 | 12 | ## What's New 13 | These release notes describe the new changes and enhancements in this version. 14 | 15 | ### Enhancements 16 | * The **kubeslice-cli** tool now allows uninstalling Kubeslice components using a custom topology file. -------------------------------------------------------------------------------- /versioned_docs/version-0.6.0/release-notes/release-notes-for-kubeslice-oss-0.5.1.mdx: -------------------------------------------------------------------------------- 1 | # Release Notes for KubeSlice OSS 0.5.0 v1 2 | 3 | *Release date: 06 Jan 2023* 4 | 5 | KubeSlice is a ***cloud-independent*** platform that combines network, application, Kubernetes, and deployment services 6 | in a framework to accelerate application deployment in a multi-cluster and multi-tenant environment. KubeSlice achieves this 7 | by creating logical application ***slice*** boundaries that enable seamless communication between pods and services across 8 | clusters, clouds, edges, and data centers. 9 | 10 | We continue to add new features and enhancements to KubeSlice. 11 | 12 | ## What's New 13 | These release notes describe the new changes and enhancements in this version. 14 | 15 | ### Enhancements 16 | * The **kubeslice-cli** tool now allows uninstalling Kubeslice components using a custom topology file. -------------------------------------------------------------------------------- /versioned_docs/version-0.7.0/release-notes/release-notes-for-kubeslice-oss-0.5.1.mdx: -------------------------------------------------------------------------------- 1 | # Release Notes for KubeSlice OSS 0.5.0 v1 2 | 3 | *Release date: 06 Jan 2023* 4 | 5 | KubeSlice is a ***cloud-independent*** platform that combines network, application, Kubernetes, and deployment services 6 | in a framework to accelerate application deployment in a multi-cluster and multi-tenant environment. KubeSlice achieves this 7 | by creating logical application ***slice*** boundaries that enable seamless communication between pods and services across 8 | clusters, clouds, edges, and data centers. 9 | 10 | We continue to add new features and enhancements to KubeSlice. 11 | 12 | ## What's New 13 | These release notes describe the new changes and enhancements in this version. 14 | 15 | ### Enhancements 16 | * The **kubeslice-cli** tool now allows uninstalling Kubeslice components using a custom topology file. -------------------------------------------------------------------------------- /versioned_docs/version-1.0.0/release-notes/release-notes-for-kubeslice-oss-0.5.1.mdx: -------------------------------------------------------------------------------- 1 | # Release Notes for KubeSlice OSS 0.5.0 v1 2 | 3 | *Release date: 06 Jan 2023* 4 | 5 | KubeSlice is a ***cloud-independent*** platform that combines network, application, Kubernetes, and deployment services 6 | in a framework to accelerate application deployment in a multi-cluster and multi-tenant environment. KubeSlice achieves this 7 | by creating logical application ***slice*** boundaries that enable seamless communication between pods and services across 8 | clusters, clouds, edges, and data centers. 9 | 10 | We continue to add new features and enhancements to KubeSlice. 11 | 12 | ## What's New 13 | These release notes describe the new changes and enhancements in this version. 14 | 15 | ### Enhancements 16 | * The **kubeslice-cli** tool now allows uninstalling Kubeslice components using a custom topology file. -------------------------------------------------------------------------------- /versioned_docs/version-1.1.0/release-notes/release-notes-for-kubeslice-oss-0.5.1.mdx: -------------------------------------------------------------------------------- 1 | # Release Notes for KubeSlice OSS 0.5.0 v1 2 | 3 | *Release date: 06 Jan 2023* 4 | 5 | KubeSlice is a ***cloud-independent*** platform that combines network, application, Kubernetes, and deployment services 6 | in a framework to accelerate application deployment in a multi-cluster and multi-tenant environment. KubeSlice achieves this 7 | by creating logical application ***slice*** boundaries that enable seamless communication between pods and services across 8 | clusters, clouds, edges, and data centers. 9 | 10 | We continue to add new features and enhancements to KubeSlice. 11 | 12 | ## What's New 13 | These release notes describe the new changes and enhancements in this version. 14 | 15 | ### Enhancements 16 | * The **kubeslice-cli** tool now allows uninstalling Kubeslice components using a custom topology file. -------------------------------------------------------------------------------- /versioned_docs/version-1.2.0/release-notes/release-notes-for-kubeslice-oss-0.5.1.mdx: -------------------------------------------------------------------------------- 1 | # Release Notes for KubeSlice OSS 0.5.0 v1 2 | 3 | *Release date: 06 Jan 2023* 4 | 5 | KubeSlice is a ***cloud-independent*** platform that combines network, application, Kubernetes, and deployment services 6 | in a framework to accelerate application deployment in a multi-cluster and multi-tenant environment. KubeSlice achieves this 7 | by creating logical application ***slice*** boundaries that enable seamless communication between pods and services across 8 | clusters, clouds, edges, and data centers. 9 | 10 | We continue to add new features and enhancements to KubeSlice. 11 | 12 | ## What's New 13 | These release notes describe the new changes and enhancements in this version. 14 | 15 | ### Enhancements 16 | * The **kubeslice-cli** tool now allows uninstalling Kubeslice components using a custom topology file. -------------------------------------------------------------------------------- /versioned_docs/version-1.3.0/release-notes/release-notes-for-kubeslice-oss-0.5.1.mdx: -------------------------------------------------------------------------------- 1 | # Release Notes for KubeSlice OSS 0.5.0 v1 2 | 3 | *Release date: 06 Jan 2023* 4 | 5 | KubeSlice is a ***cloud-independent*** platform that combines network, application, Kubernetes, and deployment services 6 | in a framework to accelerate application deployment in a multi-cluster and multi-tenant environment. KubeSlice achieves this 7 | by creating logical application ***slice*** boundaries that enable seamless communication between pods and services across 8 | clusters, clouds, edges, and data centers. 9 | 10 | We continue to add new features and enhancements to KubeSlice. 11 | 12 | ## What's New 13 | These release notes describe the new changes and enhancements in this version. 14 | 15 | ### Enhancements 16 | * The **kubeslice-cli** tool now allows uninstalling Kubeslice components using a custom topology file. -------------------------------------------------------------------------------- /versioned_docs/version-1.4.0/release-notes/release-notes-for-kubeslice-oss-0.5.1.mdx: -------------------------------------------------------------------------------- 1 | # Release Notes for KubeSlice OSS 0.5.0 v1 2 | 3 | *Release date: 06 Jan 2023* 4 | 5 | KubeSlice is a ***cloud-independent*** platform that combines network, application, Kubernetes, and deployment services 6 | in a framework to accelerate application deployment in a multi-cluster and multi-tenant environment. KubeSlice achieves this 7 | by creating logical application ***slice*** boundaries that enable seamless communication between pods and services across 8 | clusters, clouds, edges, and data centers. 9 | 10 | We continue to add new features and enhancements to KubeSlice. 11 | 12 | ## What's New 13 | These release notes describe the new changes and enhancements in this version. 14 | 15 | ### Enhancements 16 | * The **kubeslice-cli** tool now allows uninstalling Kubeslice components using a custom topology file. -------------------------------------------------------------------------------- /versioned_docs/version-1.4.0/release-notes/release-notes-for-kubeslice-oss-1.4.0.mdx: -------------------------------------------------------------------------------- 1 | # Release Notes for KubeSlice OSS 1.4.0 2 | 3 | *Release date: 25th Feb 2025* 4 | 5 | KubeSlice is a ***cloud-independent*** platform that combines network, application, Kubernetes, and deployment services 6 | in a framework to accelerate application deployment in a multi-cluster and multi-tenant environment. KubeSlice achieves this 7 | by creating logical application ***slice*** boundaries that enable seamless communication between pods and services across 8 | clusters, clouds, edges, and data centers. 9 | 10 | We continue to add new features and enhancements to KubeSlice. 11 | 12 | ## What's New :speaker: 13 | These release notes describe the new changes and enhancements in this version. 14 | 15 | * Bug fixes and security enhancements 16 | * Support for the default slice (catch all slice) 17 | * CRD API updates -------------------------------------------------------------------------------- /versioned_docs/version-1.3.0/release-notes/release-notes-for-kubeslice-oss-1.3.0.mdx: -------------------------------------------------------------------------------- 1 | # Release Notes for KubeSlice OSS 1.3.0 2 | 3 | *Release date: 2nd Apr 2024* 4 | 5 | KubeSlice is a ***cloud-independent*** platform that combines network, application, Kubernetes, and deployment services 6 | in a framework to accelerate application deployment in a multi-cluster and multi-tenant environment. KubeSlice achieves this 7 | by creating logical application ***slice*** boundaries that enable seamless communication between pods and services across 8 | clusters, clouds, edges, and data centers. 9 | 10 | We continue to add new features and enhancements to KubeSlice. 11 | 12 | ## What's New :speaker: 13 | These release notes describe the new changes and enhancements in this version. 14 | 15 | * We have made security vulnerability fixes and dependency upgrades. 16 | * We have restructured helm charts. 17 | * We have added modifications to support the feature roadmap in the near future. -------------------------------------------------------------------------------- /versioned_docs/version-1.4.0/release-notes/release-notes-for-kubeslice-oss-1.3.0.mdx: -------------------------------------------------------------------------------- 1 | # Release Notes for KubeSlice OSS 1.3.0 2 | 3 | *Release date: 2nd Apr 2024* 4 | 5 | KubeSlice is a ***cloud-independent*** platform that combines network, application, Kubernetes, and deployment services 6 | in a framework to accelerate application deployment in a multi-cluster and multi-tenant environment. KubeSlice achieves this 7 | by creating logical application ***slice*** boundaries that enable seamless communication between pods and services across 8 | clusters, clouds, edges, and data centers. 9 | 10 | We continue to add new features and enhancements to KubeSlice. 11 | 12 | ## What's New :speaker: 13 | These release notes describe the new changes and enhancements in this version. 14 | 15 | * We have made security vulnerability fixes and dependency upgrades. 16 | * We have restructured helm charts. 17 | * We have added modifications to support the feature roadmap in the near future. -------------------------------------------------------------------------------- /src/theme/DocSidebar/Desktop/styles.module.css: -------------------------------------------------------------------------------- 1 | @media (min-width: 997px) { 2 | .sidebar { 3 | display: flex; 4 | flex-direction: column; 5 | max-height: 100vh; 6 | height: 100%; 7 | position: sticky; 8 | top: 0; 9 | padding-top: var(--ifm-navbar-height); 10 | width: var(--doc-sidebar-width); 11 | transition: opacity 50ms ease; 12 | } 13 | 14 | .sidebarWithHideableNavbar { 15 | padding-top: 0; 16 | } 17 | 18 | .sidebarHidden { 19 | opacity: 0; 20 | height: 0; 21 | overflow: hidden; 22 | visibility: hidden; 23 | } 24 | 25 | .sidebarLogo { 26 | display: flex !important; 27 | align-items: center; 28 | margin: 0 var(--ifm-navbar-padding-horizontal); 29 | min-height: var(--ifm-navbar-height); 30 | max-height: var(--ifm-navbar-height); 31 | color: inherit !important; 32 | text-decoration: none !important; 33 | } 34 | 35 | .sidebarLogo img { 36 | margin-right: 0.5rem; 37 | height: 2rem; 38 | } 39 | } 40 | 41 | .sidebarLogo { 42 | display: none; 43 | } 44 | -------------------------------------------------------------------------------- /src/theme/DocSidebar/Desktop/index.js: -------------------------------------------------------------------------------- 1 | import React from 'react'; 2 | import clsx from 'clsx'; 3 | import {useThemeConfig} from '@docusaurus/theme-common'; 4 | import Logo from '@theme/Logo'; 5 | import CollapseButton from '@theme/DocSidebar/Desktop/CollapseButton'; 6 | import Content from '@theme/DocSidebar/Desktop/Content'; 7 | import styles from './styles.module.css'; 8 | function DocSidebarDesktop({path, sidebar, onCollapse, isHidden}) { 9 | const { 10 | navbar: {hideOnScroll}, 11 | docs: { 12 | sidebar: {hideable}, 13 | }, 14 | } = useThemeConfig(); 15 | return ( 16 |
22 | {hideOnScroll && } 23 | 24 | 25 | {hideable && } 26 |
27 | ); 28 | } 29 | export default React.memo(DocSidebarDesktop); 30 | -------------------------------------------------------------------------------- /versioned_docs/version-1.3.0/release-notes/release-notes-for-kubeslice-oss-1.3.1-cli.mdx: -------------------------------------------------------------------------------- 1 | # Release Notes for KubeSlice OSS 1.3.1 - kubeslice-cli 2 | 3 | *Release date: 26th Apr 2024* 4 | 5 | KubeSlice is a ***cloud-independent*** platform that combines network, application, Kubernetes, and deployment services 6 | in a framework to accelerate application deployment in a multi-cluster and multi-tenant environment. KubeSlice achieves this 7 | by creating logical application ***slice*** boundaries that enable seamless communication between pods and services across 8 | clusters, clouds, edges, and data centers. 9 | 10 | We continue to add new features and enhancements to KubeSlice. 11 | 12 | ## What's New :speaker: 13 | 14 | ### Installing KubeSlice in the Air-Gapped Environment using the kubeslice-cli Tool 15 | 16 | The kubeslice-cli version 0.6.0 now supports the installation of KubeSlice using local helm chart repositories. Thus the tool supports the 17 | installation in the air-gapped environment. For more information, see [how to install KubeSlice in the air-gapped environment](/versioned_docs/version-1.3.0/install-kubeslice/kubeslice-cli/install-kubeslice.mdx#air-gapped-installation). -------------------------------------------------------------------------------- /versioned_docs/version-1.4.0/release-notes/release-notes-for-kubeslice-oss-1.3.1-cli.mdx: -------------------------------------------------------------------------------- 1 | # Release Notes for KubeSlice OSS 1.3.1 - kubeslice-cli 2 | 3 | *Release date: 26th Apr 2024* 4 | 5 | KubeSlice is a ***cloud-independent*** platform that combines network, application, Kubernetes, and deployment services 6 | in a framework to accelerate application deployment in a multi-cluster and multi-tenant environment. KubeSlice achieves this 7 | by creating logical application ***slice*** boundaries that enable seamless communication between pods and services across 8 | clusters, clouds, edges, and data centers. 9 | 10 | We continue to add new features and enhancements to KubeSlice. 11 | 12 | ## What's New :speaker: 13 | 14 | ### Installing KubeSlice in the Air-Gapped Environment using the kubeslice-cli Tool 15 | 16 | The kubeslice-cli version 0.6.0 now supports the installation of KubeSlice using local helm chart repositories. Thus the tool supports the 17 | installation in the air-gapped environment. For more information, see [how to install KubeSlice in the air-gapped environment](/versioned_docs/version-1.3.0/install-kubeslice/kubeslice-cli/install-kubeslice.mdx#air-gapped-installation). -------------------------------------------------------------------------------- /versioned_docs/version-1.1.0/release-notes/release-notes-for-kubeslice-oss-0.4.0.mdx: -------------------------------------------------------------------------------- 1 | # Release Notes for KubeSlice OSS 0.4.0 2 | 3 | *Release date: 12th October 2022* 4 | 5 | KubeSlice is a ***cloud-independent*** platform that combines network, application, Kubernetes, and deployment services in a framework to accelerate application deployment in a multi-cluster and multi-tenant environment. KubeSlice achieves this by creating logical application ***slice*** boundaries which allow pods and services to communicate seamlessly across clusters, clouds, edges, and data centres. 6 | 7 | We continue to add new features and enhancements to KubeSlice. 8 | 9 | ## What's New 10 | These release notes describe the new changes and enhancements in this version. 11 | 12 | ### IP Address Management 13 | For managing and monitoring IP addresses on a slice, a new parameter has been introduced 14 | to configure the maximum number of clusters that can be connected to a slice. This parameter 15 | is configurable only during slice creation. The value is immutable after the slice creation. 16 | 17 | For more information, see the [slice configuration](/versioned_docs/version-1.1.0/install-kubeslice/yaml/slice-operations/slice-operations-slice-creation.mdx). -------------------------------------------------------------------------------- /versioned_docs/version-1.0.0/release-notes/release-notes-for-kubeslice-oss-0.4.0.mdx: -------------------------------------------------------------------------------- 1 | # Release Notes for KubeSlice OSS 0.4.0 2 | 3 | *Release date: 12th October 2022* 4 | 5 | KubeSlice is a ***cloud-independent*** platform that combines network, application, Kubernetes, and deployment services in a framework to accelerate application deployment in a multi-cluster and multi-tenant environment. KubeSlice achieves this by creating logical application ***slice*** boundaries which allow pods and services to communicate seamlessly across clusters, clouds, edges, and data centres. 6 | 7 | We continue to add new features and enhancements to KubeSlice. 8 | 9 | ## What's New 10 | These release notes describe the new changes and enhancements in this version. 11 | 12 | ### IP Address Management 13 | For managing and monitoring IP addresses on a slice, a new parameter has been introduced 14 | to configure the maximum number of clusters that can be connected to a slice. This parameter 15 | is configurable only during slice creation. The value is immutable after the slice creation. 16 | 17 | For more information, see the [slice configuration](/versioned_docs/version-1.1.0/install-kubeslice/yaml/slice-operations/slice-operations-slice-creation.mdx#slice-creation). -------------------------------------------------------------------------------- /versioned_docs/version-1.2.0/release-notes/release-notes-for-kubeslice-oss-0.4.0.mdx: -------------------------------------------------------------------------------- 1 | # Release Notes for KubeSlice OSS 0.4.0 2 | 3 | *Release date: 12th October 2022* 4 | 5 | KubeSlice is a ***cloud-independent*** platform that combines network, application, Kubernetes, and deployment services in a framework to accelerate application deployment in a multi-cluster and multi-tenant environment. KubeSlice achieves this by creating logical application ***slice*** boundaries which allow pods and services to communicate seamlessly across clusters, clouds, edges, and data centres. 6 | 7 | We continue to add new features and enhancements to KubeSlice. 8 | 9 | ## What's New 10 | These release notes describe the new changes and enhancements in this version. 11 | 12 | ### IP Address Management 13 | For managing and monitoring IP addresses on a slice, a new parameter has been introduced 14 | to configure the maximum number of clusters that can be connected to a slice. This parameter 15 | is configurable only during slice creation. The value is immutable after the slice creation. 16 | 17 | For more information, see the [slice configuration](/versioned_docs/version-1.2.0/install-kubeslice/yaml/slice-operations/slice-operations-slice-creation.mdx#slice-creation). -------------------------------------------------------------------------------- /versioned_docs/version-1.3.0/release-notes/release-notes-for-kubeslice-oss-0.4.0.mdx: -------------------------------------------------------------------------------- 1 | # Release Notes for KubeSlice OSS 0.4.0 2 | 3 | *Release date: 12th October 2022* 4 | 5 | KubeSlice is a ***cloud-independent*** platform that combines network, application, Kubernetes, and deployment services in a framework to accelerate application deployment in a multi-cluster and multi-tenant environment. KubeSlice achieves this by creating logical application ***slice*** boundaries which allow pods and services to communicate seamlessly across clusters, clouds, edges, and data centres. 6 | 7 | We continue to add new features and enhancements to KubeSlice. 8 | 9 | ## What's New 10 | These release notes describe the new changes and enhancements in this version. 11 | 12 | ### IP Address Management 13 | For managing and monitoring IP addresses on a slice, a new parameter has been introduced 14 | to configure the maximum number of clusters that can be connected to a slice. This parameter 15 | is configurable only during slice creation. The value is immutable after the slice creation. 16 | 17 | For more information, see the [slice configuration](/versioned_docs/version-1.3.0/install-kubeslice/yaml/slice-operations/slice-operations-slice-creation.mdx#slice-creation). -------------------------------------------------------------------------------- /versioned_docs/version-1.4.0/release-notes/release-notes-for-kubeslice-oss-0.4.0.mdx: -------------------------------------------------------------------------------- 1 | # Release Notes for KubeSlice OSS 0.4.0 2 | 3 | *Release date: 12th October 2022* 4 | 5 | KubeSlice is a ***cloud-independent*** platform that combines network, application, Kubernetes, and deployment services in a framework to accelerate application deployment in a multi-cluster and multi-tenant environment. KubeSlice achieves this by creating logical application ***slice*** boundaries which allow pods and services to communicate seamlessly across clusters, clouds, edges, and data centres. 6 | 7 | We continue to add new features and enhancements to KubeSlice. 8 | 9 | ## What's New 10 | These release notes describe the new changes and enhancements in this version. 11 | 12 | ### IP Address Management 13 | For managing and monitoring IP addresses on a slice, a new parameter has been introduced 14 | to configure the maximum number of clusters that can be connected to a slice. This parameter 15 | is configurable only during slice creation. The value is immutable after the slice creation. 16 | 17 | For more information, see the [slice configuration](/versioned_docs/version-1.3.0/install-kubeslice/yaml/slice-operations/slice-operations-slice-creation.mdx#slice-creation). -------------------------------------------------------------------------------- /versioned_docs/version-0.4.0/release-notes/release-notes-for-kubeslice-oss-0.4.0.mdx: -------------------------------------------------------------------------------- 1 | # Release Notes for KubeSlice OSS 0.4.0 2 | 3 | *Release date: 12th October 2022* 4 | 5 | KubeSlice is a ***cloud-independent*** platform that combines network, application, Kubernetes, and deployment services in a framework to accelerate application deployment in a multi-cluster and multi-tenant environment. KubeSlice achieves this by creating logical application ***slice*** boundaries which allow pods and services to communicate seamlessly across clusters, clouds, edges, and data centres. 6 | 7 | We continue to add new features and enhancements to KubeSlice. 8 | 9 | ## What's New 10 | These release notes describe the new changes and enhancements in this version. 11 | 12 | ### IP Address Management 13 | For managing and monitoring IP addresses on a slice, a new parameter has been introduced 14 | to configure the maximum number of clusters that can be connected to a slice. This parameter 15 | is configurable only during slice creation. The value is immutable after the slice creation. 16 | 17 | For more information, see the [slice configuration](/versioned_docs/version-0.4.0/getting-started-with-cloud-clusters/installing-kubeslice/creating-a-slice.mdx#creating-the-slice-yaml-file). -------------------------------------------------------------------------------- /versioned_docs/version-0.5.0/release-notes/release-notes-for-kubeslice-oss-0.4.0.mdx: -------------------------------------------------------------------------------- 1 | # Release Notes for KubeSlice OSS 0.4.0 2 | 3 | *Release date: 12th October 2022* 4 | 5 | KubeSlice is a ***cloud-independent*** platform that combines network, application, Kubernetes, and deployment services in a framework to accelerate application deployment in a multi-cluster and multi-tenant environment. KubeSlice achieves this by creating logical application ***slice*** boundaries which allow pods and services to communicate seamlessly across clusters, clouds, edges, and data centres. 6 | 7 | We continue to add new features and enhancements to KubeSlice. 8 | 9 | ## What's New 10 | These release notes describe the new changes and enhancements in this version. 11 | 12 | ### IP Address Management 13 | For managing and monitoring IP addresses on a slice, a new parameter has been introduced 14 | to configure the maximum number of clusters that can be connected to a slice. This parameter 15 | is configurable only during slice creation. The value is immutable after the slice creation. 16 | 17 | For more information, see the [slice configuration](/versioned_docs/version-0.5.0/getting-started-with-cloud-clusters/installing-kubeslice/creating-a-slice.mdx#creating-the-slice-yaml-file). -------------------------------------------------------------------------------- /versioned_docs/version-0.6.0/release-notes/release-notes-for-kubeslice-oss-0.4.0.mdx: -------------------------------------------------------------------------------- 1 | # Release Notes for KubeSlice OSS 0.4.0 2 | 3 | *Release date: 12th October 2022* 4 | 5 | KubeSlice is a ***cloud-independent*** platform that combines network, application, Kubernetes, and deployment services in a framework to accelerate application deployment in a multi-cluster and multi-tenant environment. KubeSlice achieves this by creating logical application ***slice*** boundaries which allow pods and services to communicate seamlessly across clusters, clouds, edges, and data centres. 6 | 7 | We continue to add new features and enhancements to KubeSlice. 8 | 9 | ## What's New 10 | These release notes describe the new changes and enhancements in this version. 11 | 12 | ### IP Address Management 13 | For managing and monitoring IP addresses on a slice, a new parameter has been introduced 14 | to configure the maximum number of clusters that can be connected to a slice. This parameter 15 | is configurable only during slice creation. The value is immutable after the slice creation. 16 | 17 | For more information, see the [slice configuration](/versioned_docs/version-0.5.0/getting-started-with-cloud-clusters/installing-kubeslice/creating-a-slice.mdx#creating-the-slice-yaml-file). -------------------------------------------------------------------------------- /versioned_docs/version-0.7.0/release-notes/release-notes-for-kubeslice-oss-0.4.0.mdx: -------------------------------------------------------------------------------- 1 | # Release Notes for KubeSlice OSS 0.4.0 2 | 3 | *Release date: 12th October 2022* 4 | 5 | KubeSlice is a ***cloud-independent*** platform that combines network, application, Kubernetes, and deployment services in a framework to accelerate application deployment in a multi-cluster and multi-tenant environment. KubeSlice achieves this by creating logical application ***slice*** boundaries which allow pods and services to communicate seamlessly across clusters, clouds, edges, and data centres. 6 | 7 | We continue to add new features and enhancements to KubeSlice. 8 | 9 | ## What's New 10 | These release notes describe the new changes and enhancements in this version. 11 | 12 | ### IP Address Management 13 | For managing and monitoring IP addresses on a slice, a new parameter has been introduced 14 | to configure the maximum number of clusters that can be connected to a slice. This parameter 15 | is configurable only during slice creation. The value is immutable after the slice creation. 16 | 17 | For more information, see the [slice configuration](/versioned_docs/version-0.7.0/getting-started-with-cloud-clusters/installing-kubeslice/creating-a-slice.mdx#create-the-slice-yaml-file). -------------------------------------------------------------------------------- /.github/workflows/trivy.yaml: -------------------------------------------------------------------------------- 1 | name: trivy 2 | on: 3 | push: 4 | branches: [ "master" ] 5 | pull_request: 6 | # The branches below must be a subset of the branches above 7 | branches: [ "master" ] 8 | schedule: 9 | - cron: '29 19 * * 6' 10 | permissions: 11 | contents: read 12 | 13 | jobs: 14 | build: 15 | permissions: 16 | contents: read # for actions/checkout to fetch code 17 | security-events: write # for github/codeql-action/upload-sarif to upload SARIF results 18 | actions: read # only required for a private repository by github/codeql-action/upload-sarif to get the Action run status 19 | name: Build 20 | runs-on: ubuntu-latest 21 | steps: 22 | - name: Checkout code 23 | uses: actions/checkout@v3 24 | 25 | - name: Run Trivy vulnerability scanner in repo mode 26 | uses: aquasecurity/trivy-action@master 27 | with: 28 | scan-type: 'repo' 29 | ignore-unfixed: true 30 | format: 'sarif' 31 | output: 'trivy-results.sarif' 32 | severity: 'CRITICAL' 33 | 34 | - name: Upload Trivy scan results to GitHub Security tab 35 | uses: github/codeql-action/upload-sarif@v2 36 | with: 37 | sarif_file: 'trivy-results.sarif' -------------------------------------------------------------------------------- /versioned_docs/version-0.4.0/getting-started-with-cloud-clusters/uninstalling-kubeslice/deleting-the-slice.mdx: -------------------------------------------------------------------------------- 1 | # Delete the Slice 2 | 3 | ## Introduction 4 | 5 | This topic describes the steps to delete the slice(s) from your cluster. The order of 6 | these steps is very important to ensure proper resource clean-up. Ensure that you have 7 | completed the tasks in the prerequisites. 8 | 9 | ## Prerequisites 10 | 11 | :::caution 12 | Offboard all the namespaces from the slice before deleting it. To know 13 | more, see [offboarding namespaces](/versioned_docs/version-0.4.0/getting-started-with-cloud-clusters/uninstalling-kubeslice/offboarding-namespaces.mdx). 14 | ::: 15 | 16 | ## Delete the Slice 17 | 18 | :::caution 19 | This step **must** be completed before uninstalling the Slice Operator. Failing to do so 20 | can result in slices and resources not being cleaned up properly. 21 | ::: 22 | 23 | Switch the context to the controller cluster using the following command: 24 | 25 | ``` 26 | kubectx 27 | ``` 28 | 29 | To delete an individual slice, use the following command: 30 | 31 | ``` 32 | kubectl delete sliceconfig -n kubeslice- 33 | ``` 34 | 35 | To delete all the slices, use the following command: 36 | 37 | ``` 38 | kubectl delete sliceconfig --all -n kubeslice- 39 | ``` -------------------------------------------------------------------------------- /versioned_docs/version-0.5.0/getting-started-with-cloud-clusters/uninstalling-kubeslice/deleting-the-slice.mdx: -------------------------------------------------------------------------------- 1 | # Delete the Slice 2 | 3 | ## Introduction 4 | 5 | This topic describes the steps to delete the slice(s) from your cluster. The order of 6 | these steps is very important to ensure proper resource clean-up. Ensure that you have 7 | completed the tasks in the prerequisites. 8 | 9 | ## Prerequisites 10 | 11 | :::caution 12 | Offboard all the namespaces from the slice before deleting it. To know 13 | more, see [offboarding namespaces](/versioned_docs/version-0.5.0/getting-started-with-cloud-clusters/uninstalling-kubeslice/offboarding-namespaces.mdx). 14 | ::: 15 | 16 | ## Delete the Slice 17 | 18 | :::caution 19 | This step **must** be completed before uninstalling the Slice Operator. Failing to do so 20 | can result in slices and resources not being cleaned up properly. 21 | ::: 22 | 23 | Switch the context to the controller cluster using the following command: 24 | 25 | ``` 26 | kubectx 27 | ``` 28 | 29 | To delete an individual slice, use the following command: 30 | 31 | ``` 32 | kubectl delete sliceconfig -n kubeslice- 33 | ``` 34 | 35 | To delete all the slices, use the following command: 36 | 37 | ``` 38 | kubectl delete sliceconfig --all -n kubeslice- 39 | ``` -------------------------------------------------------------------------------- /versioned_docs/version-0.6.0/getting-started-with-cloud-clusters/uninstalling-kubeslice/deleting-the-slice.mdx: -------------------------------------------------------------------------------- 1 | # Delete the Slice 2 | 3 | ## Introduction 4 | 5 | This topic describes the steps to delete the slice(s) from your cluster. The order of 6 | these steps is very important to ensure proper resource clean-up. Ensure that you have 7 | completed the tasks in the prerequisites. 8 | 9 | ## Prerequisites 10 | 11 | :::caution 12 | Offboard all the namespaces from the slice before deleting it. To know 13 | more, see [offboarding namespaces](/versioned_docs/version-0.6.0/getting-started-with-cloud-clusters/uninstalling-kubeslice/offboarding-namespaces.mdx). 14 | ::: 15 | 16 | ## Delete the Slice 17 | 18 | :::caution 19 | This step **must** be completed before uninstalling the Slice Operator. Failing to do so 20 | can result in slices and resources not being cleaned up properly. 21 | ::: 22 | 23 | Switch the context to the controller cluster using the following command: 24 | 25 | ``` 26 | kubectx 27 | ``` 28 | 29 | To delete an individual slice, use the following command: 30 | 31 | ``` 32 | kubectl delete sliceconfig -n kubeslice- 33 | ``` 34 | 35 | To delete all the slices, use the following command: 36 | 37 | ``` 38 | kubectl delete sliceconfig --all -n kubeslice- 39 | ``` -------------------------------------------------------------------------------- /versioned_docs/version-0.7.0/getting-started-with-cloud-clusters/uninstalling-kubeslice/deleting-the-slice.mdx: -------------------------------------------------------------------------------- 1 | # Delete the Slice 2 | 3 | ## Introduction 4 | 5 | This topic describes the steps to delete the slice(s) from your cluster. The order of 6 | these steps is very important to ensure proper resource clean-up. Ensure that you have 7 | completed the tasks in the prerequisites. 8 | 9 | ## Prerequisites 10 | 11 | :::caution 12 | Offboard all the namespaces from the slice before deleting it. To know 13 | more, see [offboarding namespaces](/versioned_docs/version-0.7.0/getting-started-with-cloud-clusters/uninstalling-kubeslice/offboarding-namespaces.mdx). 14 | ::: 15 | 16 | ## Delete the Slice 17 | 18 | :::caution 19 | This step **must** be completed before uninstalling the Slice Operator. Failing to do so 20 | can result in slices and resources not being cleaned up properly. 21 | ::: 22 | 23 | Switch the context to the controller cluster using the following command: 24 | 25 | ``` 26 | kubectx 27 | ``` 28 | 29 | To delete an individual slice, use the following command: 30 | 31 | ``` 32 | kubectl delete sliceconfig -n kubeslice- 33 | ``` 34 | 35 | To delete all the slices, use the following command: 36 | 37 | ``` 38 | kubectl delete sliceconfig --all -n kubeslice- 39 | ``` -------------------------------------------------------------------------------- /versioned_docs/version-0.2.0/getting-started-with-cloud-clusters/uninstalling-kubeslice/deleting-the-slice.mdx: -------------------------------------------------------------------------------- 1 | # Deleting the Slice 2 | 3 | ## Introduction 4 | 5 | This topic describes the steps to delete the slice(s) from your cluster. The order of 6 | these steps is very important to ensure proper resource clean-up. Ensure that you have 7 | completed the tasks in the prerequisites. 8 | 9 | ## Prerequisites 10 | 11 | :::caution 12 | Offboard all the namespaces from the slice before deleting it. To know 13 | more, see [offboarding namespaces](/versioned_docs/version-0.2.0/getting-started-with-cloud-clusters/uninstalling-kubeslice/offboarding-namespaces.mdx). 14 | ::: 15 | 16 | ## Deleting the Slice 17 | 18 | :::caution 19 | This step **must** be completed before uninstalling the Slice Operator. Failing to do so 20 | can result in slices and resources not being cleaned up properly. 21 | ::: 22 | 23 | Switch the context to the controller cluster using the following command: 24 | 25 | ``` 26 | kubectx 27 | ``` 28 | 29 | To delete an individual slice, use the following command: 30 | 31 | ``` 32 | kubectl delete sliceconfig -n kubeslice- 33 | ``` 34 | 35 | To delete all the slices, use the following command: 36 | 37 | ``` 38 | kubectl delete sliceconfig --all -n kubeslice- 39 | ``` -------------------------------------------------------------------------------- /versioned_docs/version-0.3.0/getting-started-with-cloud-clusters/uninstalling-kubeslice/deleting-the-slice.mdx: -------------------------------------------------------------------------------- 1 | # Deleting the Slice 2 | 3 | ## Introduction 4 | 5 | This topic describes the steps to delete the slice(s) from your cluster. The order of 6 | these steps is very important to ensure proper resource clean-up. Ensure that you have 7 | completed the tasks in the prerequisites. 8 | 9 | ## Prerequisites 10 | 11 | :::caution 12 | Offboard all the namespaces from the slice before deleting it. To know 13 | more, see [offboarding namespaces](/versioned_docs/version-0.3.0/getting-started-with-cloud-clusters/uninstalling-kubeslice/offboarding-namespaces.mdx). 14 | ::: 15 | 16 | ## Deleting the Slice 17 | 18 | :::caution 19 | This step **must** be completed before uninstalling the Slice Operator. Failing to do so 20 | can result in slices and resources not being cleaned up properly. 21 | ::: 22 | 23 | Switch the context to the controller cluster using the following command: 24 | 25 | ``` 26 | kubectx 27 | ``` 28 | 29 | To delete an individual slice, use the following command: 30 | 31 | ``` 32 | kubectl delete sliceconfig -n kubeslice- 33 | ``` 34 | 35 | To delete all the slices, use the following command: 36 | 37 | ``` 38 | kubectl delete sliceconfig --all -n kubeslice- 39 | ``` -------------------------------------------------------------------------------- /versioned_docs/version-1.2.0/release-notes/release-notes-for-kubeslice-oss-1.2.1.mdx: -------------------------------------------------------------------------------- 1 | # Release Notes for KubeSlice OSS 1.2.1 2 | 3 | *Release date: 13th Mar 2024* 4 | 5 | KubeSlice is a ***cloud-independent*** platform that combines network, application, Kubernetes, and deployment services 6 | in a framework to accelerate application deployment in a multi-cluster and multi-tenant environment. KubeSlice achieves this 7 | by creating logical application ***slice*** boundaries that enable seamless communication between pods and services across 8 | clusters, clouds, edges, and data centers. 9 | 10 | We continue to add new features and enhancements to KubeSlice. 11 | 12 | ## What's New :speaker: 13 | These release notes describe the new changes and enhancements in this version. 14 | 15 | 16 | ### Controller Module Version Upgrade 17 | We have upgraded the controller-runtime module to the latest version 0.16 from version 0.11 to 18 | enable future development of new reconcilers. 19 | 20 | ### Cluster Slice Connectivity 21 | We have created pod disruption budget to prevent connectivity loss between clusters of a slice 22 | during disruptions. At least one pair of slice gateway pods should be present between a pair of 23 | clusters. 24 | 25 | ## Issues fixed :wrench: 26 | * The webhook error that occurred during an application deployment on a slice is fixed. -------------------------------------------------------------------------------- /versioned_docs/version-1.3.0/release-notes/release-notes-for-kubeslice-oss-1.2.1.mdx: -------------------------------------------------------------------------------- 1 | # Release Notes for KubeSlice OSS 1.2.1 2 | 3 | *Release date: 13th Mar 2024* 4 | 5 | KubeSlice is a ***cloud-independent*** platform that combines network, application, Kubernetes, and deployment services 6 | in a framework to accelerate application deployment in a multi-cluster and multi-tenant environment. KubeSlice achieves this 7 | by creating logical application ***slice*** boundaries that enable seamless communication between pods and services across 8 | clusters, clouds, edges, and data centers. 9 | 10 | We continue to add new features and enhancements to KubeSlice. 11 | 12 | ## What's New :speaker: 13 | These release notes describe the new changes and enhancements in this version. 14 | 15 | 16 | ### Controller Module Version Upgrade 17 | We have upgraded the controller-runtime module to the latest version 0.16 from version 0.11 to 18 | enable future development of new reconcilers. 19 | 20 | ### Cluster Slice Connectivity 21 | We have created pod disruption budget to prevent connectivity loss between clusters of a slice 22 | during disruptions. At least one pair of slice gateway pods should be present between a pair of 23 | clusters. 24 | 25 | ## Issues fixed :wrench: 26 | * The webhook error that occurred during an application deployment on a slice is fixed. -------------------------------------------------------------------------------- /versioned_docs/version-1.4.0/release-notes/release-notes-for-kubeslice-oss-1.2.1.mdx: -------------------------------------------------------------------------------- 1 | # Release Notes for KubeSlice OSS 1.2.1 2 | 3 | *Release date: 13th Mar 2024* 4 | 5 | KubeSlice is a ***cloud-independent*** platform that combines network, application, Kubernetes, and deployment services 6 | in a framework to accelerate application deployment in a multi-cluster and multi-tenant environment. KubeSlice achieves this 7 | by creating logical application ***slice*** boundaries that enable seamless communication between pods and services across 8 | clusters, clouds, edges, and data centers. 9 | 10 | We continue to add new features and enhancements to KubeSlice. 11 | 12 | ## What's New :speaker: 13 | These release notes describe the new changes and enhancements in this version. 14 | 15 | 16 | ### Controller Module Version Upgrade 17 | We have upgraded the controller-runtime module to the latest version 0.16 from version 0.11 to 18 | enable future development of new reconcilers. 19 | 20 | ### Cluster Slice Connectivity 21 | We have created pod disruption budget to prevent connectivity loss between clusters of a slice 22 | during disruptions. At least one pair of slice gateway pods should be present between a pair of 23 | clusters. 24 | 25 | ## Issues fixed :wrench: 26 | * The webhook error that occurred during an application deployment on a slice is fixed. -------------------------------------------------------------------------------- /src/theme/NotFound/Content/index.js: -------------------------------------------------------------------------------- 1 | import React from 'react'; 2 | import clsx from 'clsx'; 3 | import Translate from '@docusaurus/Translate'; 4 | import Heading from '@theme/Heading'; 5 | export default function NotFoundContent({className}) { 6 | return ( 7 |
8 |
9 |
10 | 11 | 14 | Page Not Found 15 | 16 | 17 |

18 | 21 | We could not find what you were looking for. 22 | 23 |

24 |

25 | 28 | Please contact the owner of the site that linked you to the 29 | original URL and let them know their link is broken. 30 | 31 |

32 |
33 |
34 |
35 | ); 36 | } 37 | -------------------------------------------------------------------------------- /AUTHORS: -------------------------------------------------------------------------------- 1 | # Names should be added to this file as 2 | # Name or Organization 3 | # The email address is not required for organizations. 4 | 5 | # You can update this list using the following command: 6 | # 7 | # $ (head -n10 AUTHORS && git shortlog -se | sed -E 's/^\s+[0-9]+\t//') | tee AUTHORS 8 | 9 | # Please keep the list sorted. 10 | 26tanishabanik <26tanishabanik@gmail.com> 11 | AmanSarraf 12 | Bishal Das <70086051+bishal7679@users.noreply.github.com> 13 | Divya Mohan 14 | Eric Peterson 15 | Jonas Brømsø 16 | Lakshya Gupta 17 | Md Imran 18 | Priyank Upadhyay 19 | Richie Sebastian <104349170+richiesebastian@users.noreply.github.com> 20 | Sayantani Saha 21 | Tenish-Shrestha <107172285+Tenish-Shrestha@users.noreply.github.com> 22 | Ubuntu 23 | Veena 24 | amolmote 25 | dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> 26 | ranjangautam <108670005+ranjangautam@users.noreply.github.com> 27 | ranjangautam 28 | society 29 | that-backend-guy <107320806+that-backend-guy@users.noreply.github.com> 30 | uma-kt <105046156+uma-kt@users.noreply.github.com> 31 | veenamj-avesha <104770800+veenamj-avesha@users.noreply.github.com> 32 | -------------------------------------------------------------------------------- /versioned_docs/version-1.2.0/release-notes/release-notes-for-kubeslice-oss-1.2.0.mdx: -------------------------------------------------------------------------------- 1 | # Release Notes for KubeSlice OSS 1.2.0 2 | 3 | *Release date: 16th Jan 2024* 4 | 5 | KubeSlice is a ***cloud-independent*** platform that combines network, application, Kubernetes, and deployment services 6 | in a framework to accelerate application deployment in a multi-cluster and multi-tenant environment. KubeSlice achieves this 7 | by creating logical application ***slice*** boundaries that enable seamless communication between pods and services across 8 | clusters, clouds, edges, and data centers. 9 | 10 | We continue to add new features and enhancements to KubeSlice. 11 | 12 | ## What's New 13 | These release notes describe the new changes and enhancements in this version. 14 | 15 | 16 | ### KubeSlice Supports Cluster Connectivity between Public and Private Clusters 17 | KubeSlice now supports cluster connectivity to private clusters. This feature is currently configurable only using YAML. 18 | 19 | With this release, we remove the restriction for the cluster to have at least one node with a public IP address to make 20 | it part of the KubeSlice overlay network. Enabling a node with a public IP restricted the application of KubeSlice on 21 | private cloud clusters where the virtual private clouds filter out external traffic. 22 | 23 | With the new feature, KubeSlice extends its usage to such private cloud clusters through a network load balancer which 24 | can be provisioned and managed by all major cloud providers. -------------------------------------------------------------------------------- /versioned_docs/version-1.3.0/release-notes/release-notes-for-kubeslice-oss-1.2.0.mdx: -------------------------------------------------------------------------------- 1 | # Release Notes for KubeSlice OSS 1.2.0 2 | 3 | *Release date: 16th Jan 2024* 4 | 5 | KubeSlice is a ***cloud-independent*** platform that combines network, application, Kubernetes, and deployment services 6 | in a framework to accelerate application deployment in a multi-cluster and multi-tenant environment. KubeSlice achieves this 7 | by creating logical application ***slice*** boundaries that enable seamless communication between pods and services across 8 | clusters, clouds, edges, and data centers. 9 | 10 | We continue to add new features and enhancements to KubeSlice. 11 | 12 | ## What's New 13 | These release notes describe the new changes and enhancements in this version. 14 | 15 | 16 | ### KubeSlice Supports Cluster Connectivity between Public and Private Clusters 17 | KubeSlice now supports cluster connectivity to private clusters. This feature is currently configurable only using YAML. 18 | 19 | With this release, we remove the restriction for the cluster to have at least one node with a public IP address to make 20 | it part of the KubeSlice overlay network. Enabling a node with a public IP restricted the application of KubeSlice on 21 | private cloud clusters where the virtual private clouds filter out external traffic. 22 | 23 | With the new feature, KubeSlice extends its usage to such private cloud clusters through a network load balancer which 24 | can be provisioned and managed by all major cloud providers. -------------------------------------------------------------------------------- /versioned_docs/version-1.4.0/release-notes/release-notes-for-kubeslice-oss-1.2.0.mdx: -------------------------------------------------------------------------------- 1 | # Release Notes for KubeSlice OSS 1.2.0 2 | 3 | *Release date: 16th Jan 2024* 4 | 5 | KubeSlice is a ***cloud-independent*** platform that combines network, application, Kubernetes, and deployment services 6 | in a framework to accelerate application deployment in a multi-cluster and multi-tenant environment. KubeSlice achieves this 7 | by creating logical application ***slice*** boundaries that enable seamless communication between pods and services across 8 | clusters, clouds, edges, and data centers. 9 | 10 | We continue to add new features and enhancements to KubeSlice. 11 | 12 | ## What's New 13 | These release notes describe the new changes and enhancements in this version. 14 | 15 | 16 | ### KubeSlice Supports Cluster Connectivity between Public and Private Clusters 17 | KubeSlice now supports cluster connectivity to private clusters. This feature is currently configurable only using YAML. 18 | 19 | With this release, we remove the restriction for the cluster to have at least one node with a public IP address to make 20 | it part of the KubeSlice overlay network. Enabling a node with a public IP restricted the application of KubeSlice on 21 | private cloud clusters where the virtual private clouds filter out external traffic. 22 | 23 | With the new feature, KubeSlice extends its usage to such private cloud clusters through a network load balancer which 24 | can be provisioned and managed by all major cloud providers. -------------------------------------------------------------------------------- /versioned_docs/version-1.0.0/get-started/prerequisites/prerequisites-cluster-networking.mdx: -------------------------------------------------------------------------------- 1 | # Cluster Networking 2 | To ensure the proper functioning of the KubeSlice Gateway Nodes in both public and 3 | private clusters, please open the required UDP ports. 4 | 5 | | Kubernetes Service | CNI with Network Policy Support | Open UDP Ports | Reachability Options | 6 | | ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------- | ------------------------------------ | 7 | | Azure Kubernetes Service | [Enable Calico for Azure AKS](https://projectcalico.docs.tigera.io/getting-started/kubernetes/managed-public-cloud/aks#install-aks-with-calico-for-network-policy) | 30000-33000 | Public Node IP with NodePort Service | 8 | | AWS Elastic Kubernetes Service | [Enable Calico for Amazon EKS](https://docs.aws.amazon.com/eks/latest/userguide/calico.html) | 30000-33000 | Public Node IP with NodePort Service | 9 | | Google Kubernetes Engine | [Enable Calico for Google GKE](https://cloud.google.com/kubernetes-engine/docs/how-to/network-policy#enabling_network_policy_enforcement) | 30000-33000 | Public Node IP with NodePort Service | -------------------------------------------------------------------------------- /versioned_docs/version-1.1.0/get-started/prerequisites/prerequisites-cluster-networking.mdx: -------------------------------------------------------------------------------- 1 | # Cluster Networking 2 | To ensure the proper functioning of the KubeSlice Gateway Nodes in both public and 3 | private clusters, please open the required UDP ports. 4 | 5 | | Kubernetes Service | CNI with Network Policy Support | Open UDP Ports | Reachability Options | 6 | | ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------- | ------------------------------------ | 7 | | Azure Kubernetes Service | [Enable Calico for Azure AKS](https://projectcalico.docs.tigera.io/getting-started/kubernetes/managed-public-cloud/aks#install-aks-with-calico-for-network-policy) | 30000-33000 | Public Node IP with NodePort Service | 8 | | AWS Elastic Kubernetes Service | [Enable Calico for Amazon EKS](https://docs.aws.amazon.com/eks/latest/userguide/calico.html) | 30000-33000 | Public Node IP with NodePort Service | 9 | | Google Kubernetes Engine | [Enable Calico for Google GKE](https://cloud.google.com/kubernetes-engine/docs/how-to/network-policy#enabling_network_policy_enforcement) | 30000-33000 | Public Node IP with NodePort Service | -------------------------------------------------------------------------------- /versioned_docs/version-1.2.0/get-started/prerequisites/prerequisites-cluster-networking.mdx: -------------------------------------------------------------------------------- 1 | # Cluster Networking 2 | To ensure the proper functioning of the KubeSlice Gateway Nodes in both public and 3 | private clusters, please open the required UDP ports. 4 | 5 | | Kubernetes Service | CNI with Network Policy Support | Open UDP Ports | Reachability Options | 6 | | ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------- | ------------------------------------ | 7 | | Azure Kubernetes Service | [Enable Calico for Azure AKS](https://projectcalico.docs.tigera.io/getting-started/kubernetes/managed-public-cloud/aks#install-aks-with-calico-for-network-policy) | 30000-33000 | Public Node IP with NodePort Service | 8 | | AWS Elastic Kubernetes Service | [Enable Calico for Amazon EKS](https://docs.aws.amazon.com/eks/latest/userguide/calico.html) | 30000-33000 | Public Node IP with NodePort Service | 9 | | Google Kubernetes Engine | [Enable Calico for Google GKE](https://cloud.google.com/kubernetes-engine/docs/how-to/network-policy#enabling_network_policy_enforcement) | 30000-33000 | Public Node IP with NodePort Service | -------------------------------------------------------------------------------- /versioned_docs/version-1.3.0/get-started/prerequisites/prerequisites-cluster-networking.mdx: -------------------------------------------------------------------------------- 1 | # Cluster Networking 2 | To ensure the proper functioning of the KubeSlice Gateway Nodes in both public and 3 | private clusters, please open the required UDP ports. 4 | 5 | | Kubernetes Service | CNI with Network Policy Support | Open UDP Ports | Reachability Options | 6 | | ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------- | ------------------------------------ | 7 | | Azure Kubernetes Service | [Enable Calico for Azure AKS](https://projectcalico.docs.tigera.io/getting-started/kubernetes/managed-public-cloud/aks#install-aks-with-calico-for-network-policy) | 30000-33000 | Public Node IP with NodePort Service | 8 | | AWS Elastic Kubernetes Service | [Enable Calico for Amazon EKS](https://docs.aws.amazon.com/eks/latest/userguide/calico.html) | 30000-33000 | Public Node IP with NodePort Service | 9 | | Google Kubernetes Engine | [Enable Calico for Google GKE](https://cloud.google.com/kubernetes-engine/docs/how-to/network-policy#enabling_network_policy_enforcement) | 30000-33000 | Public Node IP with NodePort Service | -------------------------------------------------------------------------------- /versioned_docs/version-1.4.0/get-started/prerequisites/prerequisites-cluster-networking.mdx: -------------------------------------------------------------------------------- 1 | # Cluster Networking 2 | To ensure the proper functioning of the KubeSlice Gateway Nodes in both public and 3 | private clusters, please open the required UDP ports. 4 | 5 | | Kubernetes Service | CNI with Network Policy Support | Open UDP Ports | Reachability Options | 6 | | ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------- | ------------------------------------ | 7 | | Azure Kubernetes Service | [Enable Calico for Azure AKS](https://projectcalico.docs.tigera.io/getting-started/kubernetes/managed-public-cloud/aks#install-aks-with-calico-for-network-policy) | 30000-33000 | Public Node IP with NodePort Service | 8 | | AWS Elastic Kubernetes Service | [Enable Calico for Amazon EKS](https://docs.aws.amazon.com/eks/latest/userguide/calico.html) | 30000-33000 | Public Node IP with NodePort Service | 9 | | Google Kubernetes Engine | [Enable Calico for Google GKE](https://cloud.google.com/kubernetes-engine/docs/how-to/network-policy#enabling_network_policy_enforcement) | 30000-33000 | Public Node IP with NodePort Service | -------------------------------------------------------------------------------- /versioned_docs/version-0.6.0/features/ipam.mdx: -------------------------------------------------------------------------------- 1 | # IP Address Management 2 | 3 | IP Address Management (IPAM) is a method of planning, tracking, and managing the IP address space 4 | used in a network. The `maxClusters` parameter of the slice configuration helps with IPAM. 5 | 6 | This parameter sets the maximum number of worker clusters that you can connect to a slice. The 7 | maximum number of worker clusters affects the subnet calculation of a worker cluster. The subnet 8 | in turn determines the number of host addresses a worker cluster gets for its application pods. 9 | 10 | For example, if the slice subnet is 10.1.0.0/16 and the maximum number of clusters is 16, then each 11 | cluster gets a subnet of 10.1.x.0/20, where x = 0, 16, or 32. 12 | 13 | This is a significant parameter that can only be configured during slice creation. If this parameter is 14 | not set, it defaults to 16. 15 | 16 | :::caution 17 | The subnet of a worker cluster determines the number of host addresses that are available to that 18 | cluster. Hence, you must be prudent and cautious when you set the maximum worker clusters. The value 19 | of the maximum number of clusters set remains constant for the entire life of a slice, and it is 20 | immutable after a slice is created. 21 | ::: 22 | 23 | The fewer the clusters, the more IP addresses are available for the application pods 24 | of every worker cluster that is part of a slice. By default, the value of the **maxClusters** 25 | parameter is 16. The supported value range is 2 to 32 clusters. -------------------------------------------------------------------------------- /versioned_docs/version-0.7.0/features/ipam.mdx: -------------------------------------------------------------------------------- 1 | # IP Address Management 2 | 3 | IP Address Management (IPAM) is a method of planning, tracking, and managing the IP address space 4 | used in a network. The `maxClusters` parameter of the slice configuration helps with IPAM. 5 | 6 | This parameter sets the maximum number of worker clusters that you can connect to a slice. The 7 | maximum number of worker clusters affects the subnet calculation of a worker cluster. The subnet 8 | in turn determines the number of host addresses a worker cluster gets for its application pods. 9 | 10 | For example, if the slice subnet is 10.1.0.0/16 and the maximum number of clusters is 16, then each 11 | cluster gets a subnet of 10.1.x.0/20, where x = 0, 16, or 32. 12 | 13 | This is a significant parameter that can only be configured during slice creation. If this parameter is 14 | not set, it defaults to 16. 15 | 16 | :::caution 17 | The subnet of a worker cluster determines the number of host addresses that are available to that 18 | cluster. Hence, you must be prudent and cautious when you set the maximum worker clusters. The value 19 | of the maximum number of clusters set remains constant for the entire life of a slice, and it is 20 | immutable after a slice is created. 21 | ::: 22 | 23 | The fewer the clusters, the more IP addresses are available for the application pods 24 | of every worker cluster that is part of a slice. By default, the value of the **maxClusters** 25 | parameter is 16. The supported value range is 2 to 32 clusters. -------------------------------------------------------------------------------- /package.json: -------------------------------------------------------------------------------- 1 | { 2 | "name": "my-website", 3 | "version": "0.0.0", 4 | "private": true, 5 | "scripts": { 6 | "docusaurus": "docusaurus", 7 | "start": "docusaurus start --host 0.0.0.0", 8 | "start:docker": "docusaurus start --host 0.0.0.0 --poll `10000`", 9 | "build": "docusaurus build", 10 | "swizzle": "docusaurus swizzle", 11 | "deploy": "docusaurus deploy", 12 | "clear": "docusaurus clear", 13 | "serve": "docusaurus serve --host 0.0.0.0", 14 | "write-translations": "docusaurus write-translations", 15 | "write-heading-ids": "docusaurus write-heading-ids" 16 | }, 17 | "dependencies": { 18 | "@docusaurus/core": "^3.6.2", 19 | "@docusaurus/plugin-client-redirects": "^3.6.2", 20 | "@docusaurus/plugin-content-blog": "^3.6.2", 21 | "@docusaurus/plugin-google-gtag": "^3.6.2", 22 | "@docusaurus/preset-classic": "^3.6.2", 23 | "@mdx-js/react": "^3.0.0", 24 | "clsx": "^2.1.1", 25 | "docusaurus-gtm-plugin": "^0.0.2", 26 | "docusaurus-plugin-sass": "^0.2.5", 27 | "prism-react-renderer": "^2.4.0", 28 | "react": "^18.2.0", 29 | "react-dom": "^18.2.0" 30 | }, 31 | "devDependencies": { 32 | "@docusaurus/module-type-aliases": "^3.6.2", 33 | "sass": "^1.69.5" 34 | }, 35 | "browserslist": { 36 | "production": [ 37 | ">0.5%", 38 | "not dead", 39 | "not op_mini all" 40 | ], 41 | "development": [ 42 | "last 1 chrome version", 43 | "last 1 firefox version", 44 | "last 1 safari version" 45 | ] 46 | } 47 | } 48 | -------------------------------------------------------------------------------- /versioned_docs/version-0.2.0/community.mdx: -------------------------------------------------------------------------------- 1 | # Community 2 | 3 | ## Introduction 4 | Welcome to the KubeSlice community. Join our community to learn, contribute, and get responses to your questions. 5 | 6 | Explore ways to get involved below, and stay up-to-date with the latest announcements and events. 7 | 8 | ## KubeSlice Discussions 9 | You can communicate with the maintainers and the KubeSlice community using [kubeslice discussions](https://github.com/orgs/kubeslice/discussions). 10 | 11 | The KubeSlice discussions have a few categories and some of them are described in the following table. 12 | 13 | | Topic | Category | 14 | |---------------|--------------------------------| 15 | | Discussions about KubeSlice Controller | KubeSlice Controller | 16 | | Discussions about KubeSlice Worker/Slice Operator | KubeSlice Worker/Slice Operator | 17 | | General discussions about KubeSlice features, installation, and so on. | General | 18 | 19 | ## Join KubeSlice on kubernetes [Slack](https://slack.k8s.io/) 20 | just go to browse channel and search for `kubeslice` and join ! 21 | ![kubeslice](https://user-images.githubusercontent.com/90839355/183569967-55369f84-a66a-48c1-8c9c-375c1764a974.png) 22 | 23 | 24 | ## Join KubeSlice Google Groups 25 | 26 | - *If you are a user join Kubeslice user's group [here](https://groups.google.com/g/kubeslice-users)* 27 | - *If you are a developer join KubeSlice development discussions group [here](https://groups.google.com/g/kubeslice-dev)* 28 | 29 | 30 | 31 | 32 | We welcome your contributions to make KubeSlice better. We value everyone’s contribution. 33 | -------------------------------------------------------------------------------- /versioned_docs/version-0.3.0/community.mdx: -------------------------------------------------------------------------------- 1 | # Community 2 | 3 | ## Introduction 4 | Welcome to the KubeSlice community. Join our community to learn, contribute, and get responses to your questions. 5 | 6 | Explore ways to get involved below, and stay up-to-date with the latest announcements and events. 7 | 8 | ## KubeSlice Discussions 9 | You can communicate with the maintainers and the KubeSlice community using [kubeslice discussions](https://github.com/orgs/kubeslice/discussions). 10 | 11 | The KubeSlice discussions have a few categories and some of them are described in the following table. 12 | 13 | | Topic | Category | 14 | |---------------|--------------------------------| 15 | | Discussions about KubeSlice Controller | KubeSlice Controller | 16 | | Discussions about KubeSlice Worker/Slice Operator | KubeSlice Worker/Slice Operator | 17 | | General discussions about KubeSlice features, installation, and so on. | General | 18 | 19 | ## Join KubeSlice on kubernetes [Slack](https://slack.k8s.io/) 20 | just go to browse channel and search for `kubeslice` and join ! 21 | ![kubeslice](https://user-images.githubusercontent.com/90839355/183569967-55369f84-a66a-48c1-8c9c-375c1764a974.png) 22 | 23 | 24 | ## Join KubeSlice Google Groups 25 | 26 | - *If you are a user join Kubeslice user's group [here](https://groups.google.com/g/kubeslice-users)* 27 | - *If you are a developer join KubeSlice development discussions group [here](https://groups.google.com/g/kubeslice-dev)* 28 | 29 | 30 | 31 | 32 | We welcome your contributions to make KubeSlice better. We value everyone’s contribution. 33 | -------------------------------------------------------------------------------- /versioned_docs/version-0.4.0/community.mdx: -------------------------------------------------------------------------------- 1 | # Community 2 | 3 | ## Introduction 4 | Welcome to the KubeSlice community. Join our community to learn, contribute, and get responses to your questions. 5 | 6 | Explore ways to get involved below, and stay up-to-date with the latest announcements and events. 7 | 8 | ## KubeSlice Discussions 9 | You can communicate with the maintainers and the KubeSlice community using [kubeslice discussions](https://github.com/orgs/kubeslice/discussions). 10 | 11 | The KubeSlice discussions have a few categories and some of them are described in the following table. 12 | 13 | | Topic | Category | 14 | |---------------|--------------------------------| 15 | | Discussions about KubeSlice Controller | KubeSlice Controller | 16 | | Discussions about KubeSlice Worker/Slice Operator | KubeSlice Worker/Slice Operator | 17 | | General discussions about KubeSlice features, installation, and so on. | General | 18 | 19 | ## Join KubeSlice on kubernetes [Slack](https://slack.k8s.io/) 20 | just go to browse channel and search for `kubeslice` and join ! 21 | ![kubeslice](https://user-images.githubusercontent.com/90839355/183569967-55369f84-a66a-48c1-8c9c-375c1764a974.png) 22 | 23 | 24 | ## Join KubeSlice Google Groups 25 | 26 | - *If you are a user join Kubeslice user's group [here](https://groups.google.com/g/kubeslice-users)* 27 | - *If you are a developer join KubeSlice development discussions group [here](https://groups.google.com/g/kubeslice-dev)* 28 | 29 | 30 | 31 | 32 | We welcome your contributions to make KubeSlice better. We value everyone’s contribution. 33 | -------------------------------------------------------------------------------- /versioned_docs/version-0.5.0/community.mdx: -------------------------------------------------------------------------------- 1 | # Community 2 | 3 | ## Introduction 4 | Welcome to the KubeSlice community. Join our community to learn, contribute, and get responses to your questions. 5 | 6 | Explore ways to get involved below, and stay up-to-date with the latest announcements and events. 7 | 8 | ## KubeSlice Discussions 9 | You can communicate with the maintainers and the KubeSlice community using [kubeslice discussions](https://github.com/orgs/kubeslice/discussions). 10 | 11 | The KubeSlice discussions have a few categories and some of them are described in the following table. 12 | 13 | | Topic | Category | 14 | |---------------|--------------------------------| 15 | | Discussions about KubeSlice Controller | KubeSlice Controller | 16 | | Discussions about KubeSlice Worker/Slice Operator | KubeSlice Worker/Slice Operator | 17 | | General discussions about KubeSlice features, installation, and so on. | General | 18 | 19 | ## Join KubeSlice on kubernetes [Slack](https://slack.k8s.io/) 20 | just go to browse channel and search for `kubeslice` and join ! 21 | ![kubeslice](https://user-images.githubusercontent.com/90839355/183569967-55369f84-a66a-48c1-8c9c-375c1764a974.png) 22 | 23 | 24 | ## Join KubeSlice Google Groups 25 | 26 | - *If you are a user join Kubeslice user's group [here](https://groups.google.com/g/kubeslice-users)* 27 | - *If you are a developer join KubeSlice development discussions group [here](https://groups.google.com/g/kubeslice-dev)* 28 | 29 | 30 | 31 | 32 | We welcome your contributions to make KubeSlice better. We value everyone’s contribution. 33 | -------------------------------------------------------------------------------- /versioned_docs/version-0.6.0/community.mdx: -------------------------------------------------------------------------------- 1 | # Community 2 | 3 | ## Introduction 4 | Welcome to the KubeSlice community. Join our community to learn, contribute, and get responses to your questions. 5 | 6 | Explore ways to get involved below, and stay up-to-date with the latest announcements and events. 7 | 8 | ## KubeSlice Discussions 9 | You can communicate with the maintainers and the KubeSlice community using [kubeslice discussions](https://github.com/orgs/kubeslice/discussions). 10 | 11 | The KubeSlice discussions have a few categories and some of them are described in the following table. 12 | 13 | | Topic | Category | 14 | |---------------|--------------------------------| 15 | | Discussions about KubeSlice Controller | KubeSlice Controller | 16 | | Discussions about KubeSlice Worker/Slice Operator | KubeSlice Worker/Slice Operator | 17 | | General discussions about KubeSlice features, installation, and so on. | General | 18 | 19 | ## Join KubeSlice on kubernetes [Slack](https://slack.k8s.io/) 20 | just go to browse channel and search for `kubeslice` and join ! 21 | ![kubeslice](https://user-images.githubusercontent.com/90839355/183569967-55369f84-a66a-48c1-8c9c-375c1764a974.png) 22 | 23 | 24 | ## Join KubeSlice Google Groups 25 | 26 | - *If you are a user join Kubeslice user's group [here](https://groups.google.com/g/kubeslice-users)* 27 | - *If you are a developer join KubeSlice development discussions group [here](https://groups.google.com/g/kubeslice-dev)* 28 | 29 | 30 | 31 | 32 | We welcome your contributions to make KubeSlice better. We value everyone’s contribution. 33 | -------------------------------------------------------------------------------- /versioned_docs/version-0.7.0/community.mdx: -------------------------------------------------------------------------------- 1 | # Community 2 | 3 | ## Introduction 4 | Welcome to the KubeSlice community. Join our community to learn, contribute, and get responses to your questions. 5 | 6 | Explore ways to get involved below, and stay up-to-date with the latest announcements and events. 7 | 8 | ## KubeSlice Discussions 9 | You can communicate with the maintainers and the KubeSlice community using [kubeslice discussions](https://github.com/orgs/kubeslice/discussions). 10 | 11 | The KubeSlice discussions have a few categories and some of them are described in the following table. 12 | 13 | | Topic | Category | 14 | |---------------|--------------------------------| 15 | | Discussions about KubeSlice Controller | KubeSlice Controller | 16 | | Discussions about KubeSlice Worker/Slice Operator | KubeSlice Worker/Slice Operator | 17 | | General discussions about KubeSlice features, installation, and so on. | General | 18 | 19 | ## Join KubeSlice on kubernetes [Slack](https://slack.k8s.io/) 20 | just go to browse channel and search for `kubeslice` and join ! 21 | ![kubeslice](https://user-images.githubusercontent.com/90839355/183569967-55369f84-a66a-48c1-8c9c-375c1764a974.png) 22 | 23 | 24 | ## Join KubeSlice Google Groups 25 | 26 | - *If you are a user join Kubeslice user's group [here](https://groups.google.com/g/kubeslice-users)* 27 | - *If you are a developer join KubeSlice development discussions group [here](https://groups.google.com/g/kubeslice-dev)* 28 | 29 | 30 | 31 | 32 | We welcome your contributions to make KubeSlice better. We value everyone’s contribution. 33 | -------------------------------------------------------------------------------- /versioned_docs/version-1.0.0/get-started/prerequisites/prerequisites-install-istio.mdx: -------------------------------------------------------------------------------- 1 | # Istio 2 | [Istio](http://istio.io/) is an open source service mesh that is used frequently to connect and secure 3 | microservices within a cluster. The below instructions will install istio from the 4 | helm repository chart. 5 | 6 | :::caution 7 | You can skip these steps if you have already installed the recommended Istio version on the cluster. 8 | ::: 9 | 10 | ## Install Istio 11 | Install Istio on all worker cluster(s) participating in the configuration: 12 | 13 | 1. Switch the context to the worker cluster that will be registered with the KubeSlice Controller. 14 | ``` 15 | kubectx 16 | ``` 17 | 2. Create the `istio-system` namespace using the following command: 18 | ``` 19 | kubectl create ns istio-system 20 | ``` 21 | 3. Install the `istio-base` chart from the helm repository using the following command: 22 | ``` 23 | helm install istio-base kubeslice/istio-base -n istio-system 24 | ``` 25 | 4. Install the `istio-discovery` chart from the helm repository using the following command: 26 | ``` 27 | helm install istiod kubeslice/istio-discovery -n istio-system 28 | ``` 29 | ## Validate Istio Installation 30 | 31 | Validate the installation of Istio by checking the pod status. Use the following command 32 | to check if the pods are running: 33 | ``` 34 | kubectl get pods -n istio-system 35 | ``` 36 | 37 | **Example Output** 38 | ``` 39 | NAME READY STATUS RESTARTS AGE 40 | istiod-66f576dd98-jtshj 1/1 Running 0 60s 41 | ``` -------------------------------------------------------------------------------- /versioned_docs/version-1.1.0/get-started/prerequisites/prerequisites-install-istio.mdx: -------------------------------------------------------------------------------- 1 | # Istio 2 | [Istio](http://istio.io/) is an open source service mesh that is used frequently to connect and secure 3 | microservices within a cluster. The below instructions will install istio from the 4 | helm repository chart. 5 | 6 | :::caution 7 | You can skip these steps if you have already installed the recommended Istio version on the cluster. 8 | ::: 9 | 10 | ## Install Istio 11 | Install Istio on all worker cluster(s) participating in the configuration: 12 | 13 | 1. Switch the context to the worker cluster that will be registered with the KubeSlice Controller. 14 | ``` 15 | kubectx 16 | ``` 17 | 2. Create the `istio-system` namespace using the following command: 18 | ``` 19 | kubectl create ns istio-system 20 | ``` 21 | 3. Install the `istio-base` chart from the helm repository using the following command: 22 | ``` 23 | helm install istio-base kubeslice/istio-base -n istio-system 24 | ``` 25 | 4. Install the `istio-discovery` chart from the helm repository using the following command: 26 | ``` 27 | helm install istiod kubeslice/istio-discovery -n istio-system 28 | ``` 29 | ## Validate Istio Installation 30 | 31 | Validate the installation of Istio by checking the pod status. Use the following command 32 | to check if the pods are running: 33 | ``` 34 | kubectl get pods -n istio-system 35 | ``` 36 | 37 | **Example Output** 38 | ``` 39 | NAME READY STATUS RESTARTS AGE 40 | istiod-66f576dd98-jtshj 1/1 Running 0 60s 41 | ``` -------------------------------------------------------------------------------- /versioned_docs/version-1.2.0/get-started/prerequisites/prerequisites-install-istio.mdx: -------------------------------------------------------------------------------- 1 | # Istio 2 | [Istio](http://istio.io/) is an open source service mesh that is used frequently to connect and secure 3 | microservices within a cluster. The below instructions will install istio from the 4 | helm repository chart. 5 | 6 | :::caution 7 | You can skip these steps if you have already installed the recommended Istio version on the cluster. 8 | ::: 9 | 10 | ## Install Istio 11 | Install Istio on all worker cluster(s) participating in the configuration: 12 | 13 | 1. Switch the context to the worker cluster that will be registered with the KubeSlice Controller. 14 | ``` 15 | kubectx 16 | ``` 17 | 2. Create the `istio-system` namespace using the following command: 18 | ``` 19 | kubectl create ns istio-system 20 | ``` 21 | 3. Install the `istio-base` chart from the helm repository using the following command: 22 | ``` 23 | helm install istio-base kubeslice/istio-base -n istio-system 24 | ``` 25 | 4. Install the `istio-discovery` chart from the helm repository using the following command: 26 | ``` 27 | helm install istiod kubeslice/istio-discovery -n istio-system 28 | ``` 29 | ## Validate Istio Installation 30 | 31 | Validate the installation of Istio by checking the pod status. Use the following command 32 | to check if the pods are running: 33 | ``` 34 | kubectl get pods -n istio-system 35 | ``` 36 | 37 | **Example Output** 38 | ``` 39 | NAME READY STATUS RESTARTS AGE 40 | istiod-66f576dd98-jtshj 1/1 Running 0 60s 41 | ``` -------------------------------------------------------------------------------- /versioned_docs/version-1.3.0/get-started/prerequisites/prerequisites-install-istio.mdx: -------------------------------------------------------------------------------- 1 | # Istio 2 | [Istio](http://istio.io/) is an open source service mesh that is used frequently to connect and secure 3 | microservices within a cluster. The below instructions will install istio from the 4 | helm repository chart. 5 | 6 | :::caution 7 | You can skip these steps if you have already installed the recommended Istio version on the cluster. 8 | ::: 9 | 10 | ## Install Istio 11 | Install Istio on all worker cluster(s) participating in the configuration: 12 | 13 | 1. Switch the context to the worker cluster that will be registered with the KubeSlice Controller. 14 | ``` 15 | kubectx 16 | ``` 17 | 2. Create the `istio-system` namespace using the following command: 18 | ``` 19 | kubectl create ns istio-system 20 | ``` 21 | 3. Install the `istio-base` chart from the helm repository using the following command: 22 | ``` 23 | helm install istio-base kubeslice/istio-base -n istio-system 24 | ``` 25 | 4. Install the `istio-discovery` chart from the helm repository using the following command: 26 | ``` 27 | helm install istiod kubeslice/istio-discovery -n istio-system 28 | ``` 29 | ## Validate Istio Installation 30 | 31 | Validate the installation of Istio by checking the pod status. Use the following command 32 | to check if the pods are running: 33 | ``` 34 | kubectl get pods -n istio-system 35 | ``` 36 | 37 | **Example Output** 38 | ``` 39 | NAME READY STATUS RESTARTS AGE 40 | istiod-66f576dd98-jtshj 1/1 Running 0 60s 41 | ``` -------------------------------------------------------------------------------- /versioned_docs/version-1.4.0/get-started/prerequisites/prerequisites-install-istio.mdx: -------------------------------------------------------------------------------- 1 | # Istio 2 | [Istio](http://istio.io/) is an open source service mesh that is used frequently to connect and secure 3 | microservices within a cluster. The below instructions will install istio from the 4 | helm repository chart. 5 | 6 | :::caution 7 | You can skip these steps if you have already installed the recommended Istio version on the cluster. 8 | ::: 9 | 10 | ## Install Istio 11 | Install Istio on all worker cluster(s) participating in the configuration: 12 | 13 | 1. Switch the context to the worker cluster that will be registered with the KubeSlice Controller. 14 | ``` 15 | kubectx 16 | ``` 17 | 2. Create the `istio-system` namespace using the following command: 18 | ``` 19 | kubectl create ns istio-system 20 | ``` 21 | 3. Install the `istio-base` chart from the helm repository using the following command: 22 | ``` 23 | helm install istio-base kubeslice/istio-base -n istio-system 24 | ``` 25 | 4. Install the `istio-discovery` chart from the helm repository using the following command: 26 | ``` 27 | helm install istiod kubeslice/istio-discovery -n istio-system 28 | ``` 29 | ## Validate Istio Installation 30 | 31 | Validate the installation of Istio by checking the pod status. Use the following command 32 | to check if the pods are running: 33 | ``` 34 | kubectl get pods -n istio-system 35 | ``` 36 | 37 | **Example Output** 38 | ``` 39 | NAME READY STATUS RESTARTS AGE 40 | istiod-66f576dd98-jtshj 1/1 Running 0 60s 41 | ``` -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/FEATURE.yaml: -------------------------------------------------------------------------------- 1 | name: 🚀 Enhancement request 2 | description: Suggest an improvement or a new feature for the documentation 3 | labels: 4 | - documentation 5 | - enhancement 6 | 7 | body: 8 | - type: checkboxes 9 | attributes: 10 | label: ❓ Is this an enhancement request? 11 | description: | 12 | Use this template for suggesting improvements or new features for the documentation. 13 | For reporting issues, use the "Docs issue" template instead. 14 | options: 15 | - label: My request is about improving or adding to the documentation content or website 16 | required: true 17 | - type: dropdown 18 | attributes: 19 | label: 🗄️ Area of enhancement 20 | description: What area of the documentation do you want to improve or add to? 21 | multiple: false 22 | options: 23 | - Concepts 24 | - Guides 25 | - Reference 26 | - Website design 27 | - Troubleshooting # This is the new option 28 | - Other 29 | validations: 30 | required: true 31 | - type: textarea 32 | attributes: 33 | label: 📜 Description 34 | description: | 35 | Describe the enhancement or feature that you want to see in the documentation. 36 | Explain why it is useful or important for the users or contributors. 37 | validations: 38 | required: true 39 | - type: textarea 40 | attributes: 41 | label: 💭 Suggestion 42 | description: > 43 | If you have any ideas on how to implement the enhancement or feature, share them here. 44 | You can also provide links to relevant resources or examples. 45 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/ISSUE.yml: -------------------------------------------------------------------------------- 1 | # https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema 2 | name: 🐛 Docs issue 3 | description: Report incorrect or missing content in docs, or a website issue 4 | labels: 5 | - documentation 6 | - bug 7 | 8 | body: 9 | - type: checkboxes 10 | attributes: 11 | label: ❓ Is this a docs issue? 12 | description: | 13 | Use this issue for reporting issues related to Docker documentation. 14 | For product issues, refer to the corresponding product repository. 15 | options: 16 | - label: My issue is about the documentation content or website 17 | required: true 18 | - type: dropdown 19 | attributes: 20 | label: 🗄️ Type of issue 21 | description: What type of problem are you reporting? 22 | multiple: false 23 | options: 24 | - Information is incorrect 25 | - I can't find what I'm looking for 26 | - There's a problem with the website 27 | - Crash or error 28 | - Feature not working as expected 29 | - Other 30 | validations: 31 | required: true 32 | - type: textarea 33 | attributes: 34 | label: 📜 Description 35 | description: | 36 | Briefly describe the problem that you found. 37 | validations: 38 | required: true 39 | - type: input 40 | id: location 41 | attributes: 42 | label: 🔗 Location 43 | description: Where did you find the problem? 44 | placeholder: "https://docs.kubeslice.io/" 45 | validations: 46 | required: true 47 | - type: textarea 48 | attributes: 49 | label: 💭 Suggestion 50 | description: > 51 | Let us know if you have specific ideas on how we can fix the issue. 52 | -------------------------------------------------------------------------------- /versioned_docs/version-0.6.0/release-notes/release-notes-for-kubeslice-oss-0.6.0.mdx: -------------------------------------------------------------------------------- 1 | # Release Notes for KubeSlice OSS 0.6.0 2 | 3 | *Release date: 16th Feb 2023* 4 | 5 | KubeSlice is a ***cloud-independent*** platform that combines network, application, Kubernetes, and deployment services 6 | in a framework to accelerate application deployment in a multi-cluster and multi-tenant environment. KubeSlice achieves this 7 | by creating logical application ***slice*** boundaries that enable seamless communication between pods and services across 8 | clusters, clouds, edges, and data centers. 9 | 10 | We continue to add new features and enhancements to KubeSlice. 11 | 12 | ## What's New 13 | These release notes describe the new changes and enhancements in this version. 14 | 15 | ### Latest Supported Kubernetes Version 16 | The latest Kubernetes version that we support from this release is version [1.24](https://v1-24.docs.kubernetes.io/). 17 | 18 | ### Enhancements 19 | * With the current release, **Slice Gateway** spins up two pairs of gateway pods. With multiple replicas of the VPN pods, 20 | multiple gateway nodes, and multiple network connections to the remote cluster, we now have mechanisms in place to handle 21 | failure scenarios effectively. 22 | 23 | ## Known Issues 24 | The known issues are as follows: 25 | 26 | - The Slice Gateway Redundancy is incompatible with the existing slices on the cluster. So, you must create a new slice to 27 | use the Slice Gateway Redundancy. 28 | - Sometimes, gateway pods get stuck in the `Init` state due to this [upstream NSM](https://github.com/networkservicemesh/cmd-registry-k8s/issues/362) issue. 29 | - If a node that contains the application pods and NSM webhook pod scheduled on it is restarted, the NSM containers are not injected into the application pod. 30 | This occurs as the NSM webhook pod manages the lifecycle of the NSM `mutatingwebhookconfiguration`. -------------------------------------------------------------------------------- /versioned_docs/version-0.7.0/release-notes/release-notes-for-kubeslice-oss-0.6.0.mdx: -------------------------------------------------------------------------------- 1 | # Release Notes for KubeSlice OSS 0.6.0 2 | 3 | *Release date: 16th Feb 2023* 4 | 5 | KubeSlice is a ***cloud-independent*** platform that combines network, application, Kubernetes, and deployment services 6 | in a framework to accelerate application deployment in a multi-cluster and multi-tenant environment. KubeSlice achieves this 7 | by creating logical application ***slice*** boundaries that enable seamless communication between pods and services across 8 | clusters, clouds, edges, and data centers. 9 | 10 | We continue to add new features and enhancements to KubeSlice. 11 | 12 | ## What's New 13 | These release notes describe the new changes and enhancements in this version. 14 | 15 | ### Latest Supported Kubernetes Version 16 | The latest Kubernetes version that we support from this release is version [1.24](https://v1-24.docs.kubernetes.io/). 17 | 18 | ### Enhancements 19 | * With the current release, **Slice Gateway** spins up two pairs of gateway pods. With multiple replicas of the VPN pods, 20 | multiple gateway nodes, and multiple network connections to the remote cluster, we now have mechanisms in place to handle 21 | failure scenarios effectively. 22 | 23 | ## Known Issues 24 | The known issues are as follows: 25 | 26 | - The Slice Gateway Redundancy is incompatible with the existing slices on the cluster. So, you must create a new slice to 27 | use the Slice Gateway Redundancy. 28 | - Sometimes, gateway pods get stuck in the `Init` state due to this [upstream NSM](https://github.com/networkservicemesh/cmd-registry-k8s/issues/362) issue. 29 | - If a node that contains the application pods and NSM webhook pod scheduled on it is restarted, the NSM containers are not injected into the application pod. 30 | This occurs as the NSM webhook pod manages the lifecycle of the NSM `mutatingwebhookconfiguration`. -------------------------------------------------------------------------------- /versioned_docs/version-1.0.0/release-notes/release-notes-for-kubeslice-oss-0.6.0.mdx: -------------------------------------------------------------------------------- 1 | # Release Notes for KubeSlice OSS 0.6.0 2 | 3 | *Release date: 16th Feb 2023* 4 | 5 | KubeSlice is a ***cloud-independent*** platform that combines network, application, Kubernetes, and deployment services 6 | in a framework to accelerate application deployment in a multi-cluster and multi-tenant environment. KubeSlice achieves this 7 | by creating logical application ***slice*** boundaries that enable seamless communication between pods and services across 8 | clusters, clouds, edges, and data centers. 9 | 10 | We continue to add new features and enhancements to KubeSlice. 11 | 12 | ## What's New 13 | These release notes describe the new changes and enhancements in this version. 14 | 15 | ### Latest Supported Kubernetes Version 16 | The latest Kubernetes version that we support from this release is version [1.24](https://v1-24.docs.kubernetes.io/). 17 | 18 | ### Enhancements 19 | * With the current release, **Slice Gateway** spins up two pairs of gateway pods. With multiple replicas of the VPN pods, 20 | multiple gateway nodes, and multiple network connections to the remote cluster, we now have mechanisms in place to handle 21 | failure scenarios effectively. 22 | 23 | ## Known Issues 24 | The known issues are as follows: 25 | 26 | - The Slice Gateway Redundancy is incompatible with the existing slices on the cluster. So, you must create a new slice to 27 | use the Slice Gateway Redundancy. 28 | - Sometimes, gateway pods get stuck in the `Init` state due to this [upstream NSM](https://github.com/networkservicemesh/cmd-registry-k8s/issues/362) issue. 29 | - If a node that contains the application pods and NSM webhook pod scheduled on it is restarted, the NSM containers are not injected into the application pod. 30 | This occurs as the NSM webhook pod manages the lifecycle of the NSM `mutatingwebhookconfiguration`. -------------------------------------------------------------------------------- /versioned_docs/version-1.1.0/release-notes/release-notes-for-kubeslice-oss-0.6.0.mdx: -------------------------------------------------------------------------------- 1 | # Release Notes for KubeSlice OSS 0.6.0 2 | 3 | *Release date: 16th Feb 2023* 4 | 5 | KubeSlice is a ***cloud-independent*** platform that combines network, application, Kubernetes, and deployment services 6 | in a framework to accelerate application deployment in a multi-cluster and multi-tenant environment. KubeSlice achieves this 7 | by creating logical application ***slice*** boundaries that enable seamless communication between pods and services across 8 | clusters, clouds, edges, and data centers. 9 | 10 | We continue to add new features and enhancements to KubeSlice. 11 | 12 | ## What's New 13 | These release notes describe the new changes and enhancements in this version. 14 | 15 | ### Latest Supported Kubernetes Version 16 | The latest Kubernetes version that we support from this release is version [1.24](https://v1-24.docs.kubernetes.io/). 17 | 18 | ### Enhancements 19 | * With the current release, **Slice Gateway** spins up two pairs of gateway pods. With multiple replicas of the VPN pods, 20 | multiple gateway nodes, and multiple network connections to the remote cluster, we now have mechanisms in place to handle 21 | failure scenarios effectively. 22 | 23 | ## Known Issues 24 | The known issues are as follows: 25 | 26 | - The Slice Gateway Redundancy is incompatible with the existing slices on the cluster. So, you must create a new slice to 27 | use the Slice Gateway Redundancy. 28 | - Sometimes, gateway pods get stuck in the `Init` state due to this [upstream NSM](https://github.com/networkservicemesh/cmd-registry-k8s/issues/362) issue. 29 | - If a node that contains the application pods and NSM webhook pod scheduled on it is restarted, the NSM containers are not injected into the application pod. 30 | This occurs as the NSM webhook pod manages the lifecycle of the NSM `mutatingwebhookconfiguration`. -------------------------------------------------------------------------------- /versioned_docs/version-1.2.0/release-notes/release-notes-for-kubeslice-oss-0.6.0.mdx: -------------------------------------------------------------------------------- 1 | # Release Notes for KubeSlice OSS 0.6.0 2 | 3 | *Release date: 16th Feb 2023* 4 | 5 | KubeSlice is a ***cloud-independent*** platform that combines network, application, Kubernetes, and deployment services 6 | in a framework to accelerate application deployment in a multi-cluster and multi-tenant environment. KubeSlice achieves this 7 | by creating logical application ***slice*** boundaries that enable seamless communication between pods and services across 8 | clusters, clouds, edges, and data centers. 9 | 10 | We continue to add new features and enhancements to KubeSlice. 11 | 12 | ## What's New 13 | These release notes describe the new changes and enhancements in this version. 14 | 15 | ### Latest Supported Kubernetes Version 16 | The latest Kubernetes version that we support from this release is version [1.24](https://v1-24.docs.kubernetes.io/). 17 | 18 | ### Enhancements 19 | * With the current release, **Slice Gateway** spins up two pairs of gateway pods. With multiple replicas of the VPN pods, 20 | multiple gateway nodes, and multiple network connections to the remote cluster, we now have mechanisms in place to handle 21 | failure scenarios effectively. 22 | 23 | ## Known Issues 24 | The known issues are as follows: 25 | 26 | - The Slice Gateway Redundancy is incompatible with the existing slices on the cluster. So, you must create a new slice to 27 | use the Slice Gateway Redundancy. 28 | - Sometimes, gateway pods get stuck in the `Init` state due to this [upstream NSM](https://github.com/networkservicemesh/cmd-registry-k8s/issues/362) issue. 29 | - If a node that contains the application pods and NSM webhook pod scheduled on it is restarted, the NSM containers are not injected into the application pod. 30 | This occurs as the NSM webhook pod manages the lifecycle of the NSM `mutatingwebhookconfiguration`. -------------------------------------------------------------------------------- /versioned_docs/version-1.3.0/release-notes/release-notes-for-kubeslice-oss-0.6.0.mdx: -------------------------------------------------------------------------------- 1 | # Release Notes for KubeSlice OSS 0.6.0 2 | 3 | *Release date: 16th Feb 2023* 4 | 5 | KubeSlice is a ***cloud-independent*** platform that combines network, application, Kubernetes, and deployment services 6 | in a framework to accelerate application deployment in a multi-cluster and multi-tenant environment. KubeSlice achieves this 7 | by creating logical application ***slice*** boundaries that enable seamless communication between pods and services across 8 | clusters, clouds, edges, and data centers. 9 | 10 | We continue to add new features and enhancements to KubeSlice. 11 | 12 | ## What's New 13 | These release notes describe the new changes and enhancements in this version. 14 | 15 | ### Latest Supported Kubernetes Version 16 | The latest Kubernetes version that we support from this release is version [1.24](https://v1-24.docs.kubernetes.io/). 17 | 18 | ### Enhancements 19 | * With the current release, **Slice Gateway** spins up two pairs of gateway pods. With multiple replicas of the VPN pods, 20 | multiple gateway nodes, and multiple network connections to the remote cluster, we now have mechanisms in place to handle 21 | failure scenarios effectively. 22 | 23 | ## Known Issues 24 | The known issues are as follows: 25 | 26 | - The Slice Gateway Redundancy is incompatible with the existing slices on the cluster. So, you must create a new slice to 27 | use the Slice Gateway Redundancy. 28 | - Sometimes, gateway pods get stuck in the `Init` state due to this [upstream NSM](https://github.com/networkservicemesh/cmd-registry-k8s/issues/362) issue. 29 | - If a node that contains the application pods and NSM webhook pod scheduled on it is restarted, the NSM containers are not injected into the application pod. 30 | This occurs as the NSM webhook pod manages the lifecycle of the NSM `mutatingwebhookconfiguration`. -------------------------------------------------------------------------------- /versioned_docs/version-1.4.0/release-notes/release-notes-for-kubeslice-oss-0.6.0.mdx: -------------------------------------------------------------------------------- 1 | # Release Notes for KubeSlice OSS 0.6.0 2 | 3 | *Release date: 16th Feb 2023* 4 | 5 | KubeSlice is a ***cloud-independent*** platform that combines network, application, Kubernetes, and deployment services 6 | in a framework to accelerate application deployment in a multi-cluster and multi-tenant environment. KubeSlice achieves this 7 | by creating logical application ***slice*** boundaries that enable seamless communication between pods and services across 8 | clusters, clouds, edges, and data centers. 9 | 10 | We continue to add new features and enhancements to KubeSlice. 11 | 12 | ## What's New 13 | These release notes describe the new changes and enhancements in this version. 14 | 15 | ### Latest Supported Kubernetes Version 16 | The latest Kubernetes version that we support from this release is version [1.24](https://v1-24.docs.kubernetes.io/). 17 | 18 | ### Enhancements 19 | * With the current release, **Slice Gateway** spins up two pairs of gateway pods. With multiple replicas of the VPN pods, 20 | multiple gateway nodes, and multiple network connections to the remote cluster, we now have mechanisms in place to handle 21 | failure scenarios effectively. 22 | 23 | ## Known Issues 24 | The known issues are as follows: 25 | 26 | - The Slice Gateway Redundancy is incompatible with the existing slices on the cluster. So, you must create a new slice to 27 | use the Slice Gateway Redundancy. 28 | - Sometimes, gateway pods get stuck in the `Init` state due to this [upstream NSM](https://github.com/networkservicemesh/cmd-registry-k8s/issues/362) issue. 29 | - If a node that contains the application pods and NSM webhook pod scheduled on it is restarted, the NSM containers are not injected into the application pod. 30 | This occurs as the NSM webhook pod manages the lifecycle of the NSM `mutatingwebhookconfiguration`. -------------------------------------------------------------------------------- /versioned_docs/version-0.2.0/getting-started-with-cloud-clusters/uninstalling-kubeslice/deleting-the-project.mdx: -------------------------------------------------------------------------------- 1 | # Deleting the Project 2 | 3 | ## Introduction 4 | 5 | This topic describes the steps to delete the project from the KubeSlice Controller. The 6 | order of these steps is very important to ensure proper resource clean-up. Ensure that 7 | you have completed the tasks in the prerequisites. 8 | 9 | ## Prerequisites 10 | 11 | :::caution 12 | Offboard all the namespaces from the slice before deleting it. To know 13 | more, see [offboarding namespaces](/versioned_docs/version-0.2.0/getting-started-with-cloud-clusters/uninstalling-kubeslice/offboarding-namespaces.mdx). 14 | ::: 15 | 16 | :::caution 17 | Delete all the slices from your cluster before deleting the Slice Operator. To know more, 18 | see [deleting the slice](/versioned_docs/version-0.2.0/getting-started-with-cloud-clusters/uninstalling-kubeslice/deleting-the-slice.mdx). 19 | ::: 20 | 21 | :::caution 22 | Deregister all worker clusters from the KubeSlice Controller. To know 23 | more, see [deregistering the worker cluster](/versioned_docs/version-0.2.0/getting-started-with-cloud-clusters/uninstalling-kubeslice/deregistering-the-worker-cluster.mdx). 24 | ::: 25 | 26 | ## Deleting the Project and Project Namespace 27 | Deleting the project from the KubeSlice Controller deletes the service 28 | account, namespaces, clusters, secrets, certificates, and tokens. 29 | 30 | :::info 31 | Deleting the project automatically deletes the associated project namespace. 32 | ::: 33 | 34 | Switch the context to the KubeSlice Controller. 35 | 36 | ``` 37 | kubectx 38 | ``` 39 | 40 | Delete an individual project using the following command: 41 | 42 | ``` 43 | kubectl delete projects -n kubeslice-controller 44 | ``` 45 | 46 | To delete all projects, use the following command: 47 | 48 | ``` 49 | kubectl delete projects --all -n kubeslice-controller 50 | ``` 51 | 52 | :::success 53 | You have now successfully deleted your project and the project namespace. 54 | ::: -------------------------------------------------------------------------------- /versioned_docs/version-0.3.0/getting-started-with-cloud-clusters/uninstalling-kubeslice/deleting-the-project.mdx: -------------------------------------------------------------------------------- 1 | # Deleting the Project 2 | 3 | ## Introduction 4 | 5 | This topic describes the steps to delete the project from the KubeSlice Controller. The 6 | order of these steps is very important to ensure proper resource clean-up. Ensure that 7 | you have completed the tasks in the prerequisites. 8 | 9 | ## Prerequisites 10 | 11 | :::caution 12 | Offboard all the namespaces from the slice before deleting it. To know 13 | more, see [offboarding namespaces](/versioned_docs/version-0.3.0/getting-started-with-cloud-clusters/uninstalling-kubeslice/offboarding-namespaces.mdx). 14 | ::: 15 | 16 | :::caution 17 | Delete all the slices from your cluster before deleting the Slice Operator. To know more, 18 | see [deleting the slice](/versioned_docs/version-0.3.0/getting-started-with-cloud-clusters/uninstalling-kubeslice/deleting-the-slice.mdx). 19 | ::: 20 | 21 | :::caution 22 | Deregister all worker clusters from the KubeSlice Controller. To know 23 | more, see [deregistering the worker cluster](/versioned_docs/version-0.3.0/getting-started-with-cloud-clusters/uninstalling-kubeslice/deregistering-the-worker-cluster.mdx). 24 | ::: 25 | 26 | ## Deleting the Project and Project Namespace 27 | Deleting the project from the KubeSlice Controller deletes the service 28 | account, namespaces, clusters, secrets, certificates, and tokens. 29 | 30 | :::info 31 | Deleting the project automatically deletes the associated project namespace. 32 | ::: 33 | 34 | Switch the context to the KubeSlice Controller. 35 | 36 | ``` 37 | kubectx 38 | ``` 39 | 40 | Delete an individual project using the following command: 41 | 42 | ``` 43 | kubectl delete projects -n kubeslice-controller 44 | ``` 45 | 46 | To delete all projects, use the following command: 47 | 48 | ``` 49 | kubectl delete projects --all -n kubeslice-controller 50 | ``` 51 | 52 | :::success 53 | You have now successfully deleted your project and the project namespace. 54 | ::: -------------------------------------------------------------------------------- /versioned_docs/version-0.4.0/getting-started-with-cloud-clusters/uninstalling-kubeslice/deleting-the-project.mdx: -------------------------------------------------------------------------------- 1 | # Delete the Project 2 | 3 | ## Introduction 4 | 5 | This topic describes the steps to delete the project from the KubeSlice Controller. The 6 | order of these steps is very important to ensure proper resource clean-up. Ensure that 7 | you have completed the tasks in the prerequisites. 8 | 9 | ## Prerequisites 10 | 11 | :::caution 12 | Offboard all the namespaces from the slice before deleting it. To know 13 | more, see [offboarding namespaces](/versioned_docs/version-0.4.0/getting-started-with-cloud-clusters/uninstalling-kubeslice/offboarding-namespaces.mdx). 14 | ::: 15 | 16 | :::caution 17 | Delete all the slices from your cluster before deleting the Slice Operator. To know more, 18 | see [deleting the slice](/versioned_docs/version-0.4.0/getting-started-with-cloud-clusters/uninstalling-kubeslice/deleting-the-slice.mdx). 19 | ::: 20 | 21 | :::caution 22 | Deregister all worker clusters from the KubeSlice Controller. To know 23 | more, see [deregistering the worker cluster](/versioned_docs/version-0.4.0/getting-started-with-cloud-clusters/uninstalling-kubeslice/deregistering-the-worker-cluster.mdx). 24 | ::: 25 | 26 | ## Delete the Project and Project Namespace 27 | Deleting the project from the KubeSlice Controller deletes the service 28 | account, namespaces, clusters, secrets, certificates, and tokens. 29 | 30 | :::info 31 | Deleting the project automatically deletes the associated project namespace. 32 | ::: 33 | 34 | Switch the context to the KubeSlice Controller. 35 | 36 | ``` 37 | kubectx 38 | ``` 39 | 40 | Delete an individual project using the following command: 41 | 42 | ``` 43 | kubectl delete projects -n kubeslice-controller 44 | ``` 45 | 46 | To delete all projects, use the following command: 47 | 48 | ``` 49 | kubectl delete projects --all -n kubeslice-controller 50 | ``` 51 | 52 | :::success 53 | You have now successfully deleted your project and the project namespace. 54 | ::: -------------------------------------------------------------------------------- /versioned_docs/version-0.5.0/getting-started-with-cloud-clusters/uninstalling-kubeslice/deleting-the-project.mdx: -------------------------------------------------------------------------------- 1 | # Delete the Project 2 | 3 | ## Introduction 4 | 5 | This topic describes the steps to delete the project from the KubeSlice Controller. The 6 | order of these steps is very important to ensure proper resource clean-up. Ensure that 7 | you have completed the tasks in the prerequisites. 8 | 9 | ## Prerequisites 10 | 11 | :::caution 12 | Offboard all the namespaces from the slice before deleting it. To know 13 | more, see [offboarding namespaces](/versioned_docs/version-0.5.0/getting-started-with-cloud-clusters/uninstalling-kubeslice/offboarding-namespaces.mdx). 14 | ::: 15 | 16 | :::caution 17 | Delete all the slices from your cluster before deleting the Slice Operator. To know more, 18 | see [deleting the slice](/versioned_docs/version-0.5.0/getting-started-with-cloud-clusters/uninstalling-kubeslice/deleting-the-slice.mdx). 19 | ::: 20 | 21 | :::caution 22 | Deregister all worker clusters from the KubeSlice Controller. To know 23 | more, see [deregistering the worker cluster](/versioned_docs/version-0.5.0/getting-started-with-cloud-clusters/uninstalling-kubeslice/deregistering-the-worker-cluster.mdx). 24 | ::: 25 | 26 | ## Delete the Project and Project Namespace 27 | Deleting the project from the KubeSlice Controller deletes the service 28 | account, namespaces, clusters, secrets, certificates, and tokens. 29 | 30 | :::info 31 | Deleting the project automatically deletes the associated project namespace. 32 | ::: 33 | 34 | Switch the context to the KubeSlice Controller. 35 | 36 | ``` 37 | kubectx 38 | ``` 39 | 40 | Delete an individual project using the following command: 41 | 42 | ``` 43 | kubectl delete projects -n kubeslice-controller 44 | ``` 45 | 46 | To delete all projects, use the following command: 47 | 48 | ``` 49 | kubectl delete projects --all -n kubeslice-controller 50 | ``` 51 | 52 | :::success 53 | You have now successfully deleted your project and the project namespace. 54 | ::: -------------------------------------------------------------------------------- /versioned_docs/version-0.6.0/getting-started-with-cloud-clusters/uninstalling-kubeslice/deleting-the-project.mdx: -------------------------------------------------------------------------------- 1 | # Delete the Project 2 | 3 | ## Introduction 4 | 5 | This topic describes the steps to delete the project from the KubeSlice Controller. The 6 | order of these steps is very important to ensure proper resource clean-up. Ensure that 7 | you have completed the tasks in the prerequisites. 8 | 9 | ## Prerequisites 10 | 11 | :::caution 12 | Offboard all the namespaces from the slice before deleting it. To know 13 | more, see [offboarding namespaces](/versioned_docs/version-0.6.0/getting-started-with-cloud-clusters/uninstalling-kubeslice/offboarding-namespaces.mdx). 14 | ::: 15 | 16 | :::caution 17 | Delete all the slices from your cluster before deleting the Slice Operator. To know more, 18 | see [deleting the slice](/versioned_docs/version-0.6.0/getting-started-with-cloud-clusters/uninstalling-kubeslice/deleting-the-slice.mdx). 19 | ::: 20 | 21 | :::caution 22 | Deregister all worker clusters from the KubeSlice Controller. To know 23 | more, see [deregistering the worker cluster](/versioned_docs/version-0.6.0/getting-started-with-cloud-clusters/uninstalling-kubeslice/deregistering-the-worker-cluster.mdx). 24 | ::: 25 | 26 | ## Delete the Project and Project Namespace 27 | Deleting the project from the KubeSlice Controller deletes the service 28 | account, namespaces, clusters, secrets, certificates, and tokens. 29 | 30 | :::info 31 | Deleting the project automatically deletes the associated project namespace. 32 | ::: 33 | 34 | Switch the context to the KubeSlice Controller. 35 | 36 | ``` 37 | kubectx 38 | ``` 39 | 40 | Delete an individual project using the following command: 41 | 42 | ``` 43 | kubectl delete projects -n kubeslice-controller 44 | ``` 45 | 46 | To delete all projects, use the following command: 47 | 48 | ``` 49 | kubectl delete projects --all -n kubeslice-controller 50 | ``` 51 | 52 | :::success 53 | You have now successfully deleted your project and the project namespace. 54 | ::: -------------------------------------------------------------------------------- /versioned_docs/version-0.7.0/getting-started-with-cloud-clusters/uninstalling-kubeslice/deleting-the-project.mdx: -------------------------------------------------------------------------------- 1 | # Delete the Project 2 | 3 | ## Introduction 4 | 5 | This topic describes the steps to delete the project from the KubeSlice Controller. The 6 | order of these steps is very important to ensure proper resource clean-up. Ensure that 7 | you have completed the tasks in the prerequisites. 8 | 9 | ## Prerequisites 10 | 11 | :::caution 12 | Offboard all the namespaces from the slice before deleting it. To know 13 | more, see [offboarding namespaces](/versioned_docs/version-0.7.0/getting-started-with-cloud-clusters/uninstalling-kubeslice/offboarding-namespaces.mdx). 14 | ::: 15 | 16 | :::caution 17 | Delete all the slices from your cluster before deleting the Slice Operator. To know more, 18 | see [deleting the slice](/versioned_docs/version-0.7.0/getting-started-with-cloud-clusters/uninstalling-kubeslice/deleting-the-slice.mdx). 19 | ::: 20 | 21 | :::caution 22 | Deregister all worker clusters from the KubeSlice Controller. To know 23 | more, see [deregistering the worker cluster](/versioned_docs/version-0.7.0/getting-started-with-cloud-clusters/uninstalling-kubeslice/deregistering-the-worker-cluster.mdx). 24 | ::: 25 | 26 | ## Delete the Project and Project Namespace 27 | Deleting the project from the KubeSlice Controller deletes the service 28 | account, namespaces, clusters, secrets, certificates, and tokens. 29 | 30 | :::info 31 | Deleting the project automatically deletes the associated project namespace. 32 | ::: 33 | 34 | Switch the context to the KubeSlice Controller. 35 | 36 | ``` 37 | kubectx 38 | ``` 39 | 40 | Delete an individual project using the following command: 41 | 42 | ``` 43 | kubectl delete projects -n kubeslice-controller 44 | ``` 45 | 46 | To delete all projects, use the following command: 47 | 48 | ``` 49 | kubectl delete projects --all -n kubeslice-controller 50 | ``` 51 | 52 | :::success 53 | You have now successfully deleted your project and the project namespace. 54 | ::: -------------------------------------------------------------------------------- /static/img/slack.svg: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | -------------------------------------------------------------------------------- /versioned_docs/version-0.4.0/getting-started-with-cloud-clusters/installing-kubeslice/isolating-namespaces.mdx: -------------------------------------------------------------------------------- 1 | # Isolate Namespaces 2 | 3 | ## Introduction 4 | The namespace isolation feature allows you to confine application namespaces to a slice. The associated namespaces 5 | are connected to the slice and are isolated from other namespaces in the cluster. This forms a secure inter-cluster 6 | network segment of pods, that are isolated from the rest of the pods in the clusters. The slice segmentation isolates 7 | and protects applications from each other, and reduces blast radius of failure conditions. 8 | 9 | The following figure illustrates how the namespaces are isolated from different namespaces on a worker cluster. 10 | Namespaces are isolated with respect to sending and receiving data traffic to other namespaces in a cluster. 11 | 12 | ![alt](/img/Namespace-Isolation-OS.png) 13 | 14 | ## Enable Namespace Isolation 15 | Namespace isolation is enabled by setting the isolationEnabled parameter to true and disabled by setting the 16 | same parameter to false in the slice configuration file. To know more, see [namespace isolation profile parameters](/versioned_docs/version-0.4.0/reference/configuration-parameters.mdx#namespace-isolation-profile-parameters) 17 | and the [slice configuration YAML](/versioned_docs/version-0.4.0/getting-started-with-cloud-clusters/installing-kubeslice/creating-a-slice.mdx#creating-the-slice-yaml-file) file. 18 | 19 | When the namespace isolation feature is enabled, the namespace isolation policy is 20 | applied to isolate the application namespaces. Verify the namespace isolation policy by 21 | running the following command to confirm that the namespace isolation feature is enabled: 22 | ``` 23 | kubectl get netpol -n 24 | ``` 25 | Expected Output 26 | 27 | ``` 28 | NAME POD-SELECTOR AGE 29 | peacock-bookinfo 15s 30 | ``` 31 | 32 | In the above output, `peacock` is the slice name and `bookinfo` is the onboarded 33 | namespace to which the namespace isolation policy is applied. -------------------------------------------------------------------------------- /versioned_docs/version-0.5.0/getting-started-with-cloud-clusters/installing-kubeslice/isolating-namespaces.mdx: -------------------------------------------------------------------------------- 1 | # Isolate Namespaces 2 | 3 | ## Introduction 4 | The namespace isolation feature allows you to confine application namespaces to a slice. The associated namespaces 5 | are connected to the slice and are isolated from other namespaces in the cluster. This forms a secure inter-cluster 6 | network segment of pods, that are isolated from the rest of the pods in the clusters. The slice segmentation isolates 7 | and protects applications from each other, and reduces blast radius of failure conditions. 8 | 9 | The following figure illustrates how the namespaces are isolated from different namespaces on a worker cluster. 10 | Namespaces are isolated with respect to sending and receiving data traffic to other namespaces in a cluster. 11 | 12 | ![alt](/img/Namespace-Isolation-OS.png) 13 | 14 | ## Enable Namespace Isolation 15 | Namespace isolation is enabled by setting the isolationEnabled parameter to true and disabled by setting the 16 | same parameter to false in the slice configuration file. To know more, see [namespace isolation profile parameters](/versioned_docs/version-0.5.0/reference/configuration-parameters.mdx#namespace-isolation-profile-parameters) 17 | and the [slice configuration YAML](/versioned_docs/version-0.5.0/getting-started-with-cloud-clusters/installing-kubeslice/creating-a-slice.mdx#creating-the-slice-yaml-file) file. 18 | 19 | When the namespace isolation feature is enabled, the namespace isolation policy is 20 | applied to isolate the application namespaces. Verify the namespace isolation policy by 21 | running the following command to confirm that the namespace isolation feature is enabled: 22 | ``` 23 | kubectl get netpol -n 24 | ``` 25 | Expected Output 26 | 27 | ``` 28 | NAME POD-SELECTOR AGE 29 | peacock-bookinfo 15s 30 | ``` 31 | 32 | In the above output, `peacock` is the slice name and `bookinfo` is the onboarded 33 | namespace to which the namespace isolation policy is applied. -------------------------------------------------------------------------------- /versioned_docs/version-0.6.0/getting-started-with-cloud-clusters/installing-kubeslice/isolating-namespaces.mdx: -------------------------------------------------------------------------------- 1 | # Isolate Namespaces 2 | 3 | ## Introduction 4 | The namespace isolation feature allows you to confine application namespaces to a slice. The associated namespaces 5 | are connected to the slice and are isolated from other namespaces in the cluster. This forms a secure inter-cluster 6 | network segment of pods, that are isolated from the rest of the pods in the clusters. The slice segmentation isolates 7 | and protects applications from each other, and reduces blast radius of failure conditions. 8 | 9 | The following figure illustrates how the namespaces are isolated from different namespaces on a worker cluster. 10 | Namespaces are isolated with respect to sending and receiving data traffic to other namespaces in a cluster. 11 | 12 | ![alt](/img/Namespace-Isolation-OS.png) 13 | 14 | ## Enable Namespace Isolation 15 | Namespace isolation is enabled by setting the isolationEnabled parameter to true and disabled by setting the 16 | same parameter to false in the slice configuration file. To know more, see [namespace isolation profile parameters](/versioned_docs/version-0.6.0/reference/configuration-parameters.mdx#namespace-isolation-profile-parameters) 17 | and the [slice configuration YAML](/versioned_docs/version-0.6.0/getting-started-with-cloud-clusters/installing-kubeslice/creating-a-slice.mdx#creating-the-slice-yaml-file) file. 18 | 19 | When the namespace isolation feature is enabled, the namespace isolation policy is 20 | applied to isolate the application namespaces. Verify the namespace isolation policy by 21 | running the following command to confirm that the namespace isolation feature is enabled: 22 | ``` 23 | kubectl get netpol -n 24 | ``` 25 | Expected Output 26 | 27 | ``` 28 | NAME POD-SELECTOR AGE 29 | peacock-bookinfo 15s 30 | ``` 31 | 32 | In the above output, `peacock` is the slice name and `bookinfo` is the onboarded 33 | namespace to which the namespace isolation policy is applied. -------------------------------------------------------------------------------- /versioned_docs/version-0.7.0/getting-started-with-cloud-clusters/installing-kubeslice/isolating-namespaces.mdx: -------------------------------------------------------------------------------- 1 | # Isolate Namespaces 2 | 3 | ## Introduction 4 | The namespace isolation feature allows you to confine application namespaces to a slice. The associated namespaces 5 | are connected to the slice and are isolated from other namespaces in the cluster. This forms a secure inter-cluster 6 | network segment of pods, that are isolated from the rest of the pods in the clusters. The slice segmentation isolates 7 | and protects applications from each other, and reduces blast radius of failure conditions. 8 | 9 | The following figure illustrates how the namespaces are isolated from different namespaces on a worker cluster. 10 | Namespaces are isolated with respect to sending and receiving data traffic to other namespaces in a cluster. 11 | 12 | ![alt](/img/Namespace-Isolation-OS.png) 13 | 14 | ## Enable Namespace Isolation 15 | Namespace isolation is enabled by setting the isolationEnabled parameter to true and disabled by setting the 16 | same parameter to false in the slice configuration file. To know more, see [namespace isolation profile parameters](/versioned_docs/version-0.7.0/reference/configuration-parameters.mdx#namespace-isolation-profile-parameters) 17 | and the [slice configuration YAML](/versioned_docs/version-0.7.0/getting-started-with-cloud-clusters/installing-kubeslice/creating-a-slice.mdx#create-the-slice-yaml-file) file. 18 | 19 | When the namespace isolation feature is enabled, the namespace isolation policy is 20 | applied to isolate the application namespaces. Verify the namespace isolation policy by 21 | running the following command to confirm that the namespace isolation feature is enabled: 22 | ``` 23 | kubectl get netpol -n 24 | ``` 25 | Expected Output 26 | 27 | ``` 28 | NAME POD-SELECTOR AGE 29 | peacock-bookinfo 15s 30 | ``` 31 | 32 | In the above output, `peacock` is the slice name and `bookinfo` is the onboarded 33 | namespace to which the namespace isolation policy is applied. -------------------------------------------------------------------------------- /versioned_docs/version-0.2.0/getting-started-with-cloud-clusters/installing-kubeslice/isolating-namespaces.mdx: -------------------------------------------------------------------------------- 1 | # Isolating Namespaces 2 | 3 | ## Introduction 4 | The namespace isolation feature allows you to confine application namespaces to a slice. The associated namespaces 5 | are connected to the slice and are isolated from other namespaces in the cluster. This forms a secure inter-cluster 6 | network segment of pods, that are isolated from the rest of the pods in the clusters. The slice segmentation isolates 7 | and protects applications from each other, and reduces blast radius of failure conditions. 8 | 9 | The following figure illustrates how the namespaces are isolated from different namespaces on a worker cluster. 10 | Namespaces are isolated with respect to sending and receiving data traffic to other namespaces in a cluster. 11 | 12 | ![alt](/img/Namespace-Isolation-OS.png) 13 | 14 | ## Enabling Namespace Isolation 15 | Namespace isolation is enabled by setting the isolationEnabled parameter to true and disabled by setting the 16 | same parameter to false in the slice configuration file. To know more, see [namespace isolation profile parameters](/versioned_docs/version-0.2.0/getting-started-with-cloud-clusters/installing-kubeslice/configuration-parameters.mdx#namespace-isolation-profile-parameters) 17 | and the [slice configuration YAML](/versioned_docs/version-0.2.0/getting-started-with-cloud-clusters/installing-kubeslice/creating-a-slice.mdx#creating-the-slice-yaml-file) file. 18 | 19 | When the namespace isolation feature is enabled, the namespace isolation policy is 20 | applied to isolate the application namespaces. Verify the namespace isolation policy by 21 | running the following command to confirm that the namespace isolation feature is enabled: 22 | ``` 23 | kubectl get netpol -n 24 | ``` 25 | Expected Output 26 | 27 | ``` 28 | NAME POD-SELECTOR AGE 29 | peacock-bookinfo 15s 30 | ``` 31 | 32 | In the above output, `peacock` is the slice name and `bookinfo` is the onboarded 33 | namespace to which the namespace isolation policy is applied. -------------------------------------------------------------------------------- /versioned_docs/version-0.3.0/getting-started-with-cloud-clusters/installing-kubeslice/isolating-namespaces.mdx: -------------------------------------------------------------------------------- 1 | # Isolating Namespaces 2 | 3 | ## Introduction 4 | The namespace isolation feature allows you to confine application namespaces to a slice. The associated namespaces 5 | are connected to the slice and are isolated from other namespaces in the cluster. This forms a secure inter-cluster 6 | network segment of pods, that are isolated from the rest of the pods in the clusters. The slice segmentation isolates 7 | and protects applications from each other, and reduces blast radius of failure conditions. 8 | 9 | The following figure illustrates how the namespaces are isolated from different namespaces on a worker cluster. 10 | Namespaces are isolated with respect to sending and receiving data traffic to other namespaces in a cluster. 11 | 12 | ![alt](/img/Namespace-Isolation-OS.png) 13 | 14 | ## Enabling Namespace Isolation 15 | Namespace isolation is enabled by setting the isolationEnabled parameter to true and disabled by setting the 16 | same parameter to false in the slice configuration file. To know more, see [namespace isolation profile parameters](/versioned_docs/version-0.3.0/getting-started-with-cloud-clusters/installing-kubeslice/configuration-parameters.mdx#namespace-isolation-profile-parameters) 17 | and the [slice configuration YAML](/versioned_docs/version-0.3.0/getting-started-with-cloud-clusters/installing-kubeslice/creating-a-slice.mdx#creating-the-slice-yaml-file) file. 18 | 19 | When the namespace isolation feature is enabled, the namespace isolation policy is 20 | applied to isolate the application namespaces. Verify the namespace isolation policy by 21 | running the following command to confirm that the namespace isolation feature is enabled: 22 | ``` 23 | kubectl get netpol -n 24 | ``` 25 | Expected Output 26 | 27 | ``` 28 | NAME POD-SELECTOR AGE 29 | peacock-bookinfo 15s 30 | ``` 31 | 32 | In the above output, `peacock` is the slice name and `bookinfo` is the onboarded 33 | namespace to which the namespace isolation policy is applied. -------------------------------------------------------------------------------- /versioned_docs/version-1.0.0/get-started/prerequisites/prerequisites-command-line-tools.mdx: -------------------------------------------------------------------------------- 1 | # Command Line Tools 2 | This section of the documentation aims to meet the requirements for product installations 3 | by providing information about the necessary prerequisites for installing KubeSlice. 4 | It is essential to have a well-configured environment that fulfills the installation 5 | requirements for KubeSlice. This involves the installation of the KubeSlice Controller 6 | and registering clusters with it. This topic will explain the prerequisites in detail to 7 | help you successfully install KubeSlice. 8 | 9 | ## Required Tools 10 | To make the installation process of KubeSlice smoother and more accessible, we have listed the 11 | required command line tools below. With these tools readily available, you can easily install 12 | KubeSlice and start benefiting from its features. 13 | 14 | | Package Required | Installation Instructions | 15 | | ----------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- | 16 | | [Helm](https://helm.sh) - The Package Manager for Kubernetes | [Installing Helm](https://helm.sh/docs/intro/install/) | 17 | | [kubectl](https://kubernetes.io/docs/reference/kubectl/overview) - Kubernetes CLI | [Installing kubectl](https://kubernetes.io/docs/tasks/tools/) | 18 | | [kubectx and kubens](https://github.com/ahmetb/kubectx) - Cluster Context Switching & Namespace Assignments | [Installing kubectx & kubens](https://github.com/ahmetb/kubectx#installation) | 19 | | [kubeslice-cli ](https://github.com/kubeslice/kubeslice-cli/releases)- KubeSlice Installer Binaries | [Installing kubeslice-cli](/get-started/prerequisites/prerequisites-kubeslice-cli-install.mdx) | 20 | -------------------------------------------------------------------------------- /versioned_docs/version-1.1.0/get-started/prerequisites/prerequisites-command-line-tools.mdx: -------------------------------------------------------------------------------- 1 | # Command Line Tools 2 | This section of the documentation aims to meet the requirements for product installations 3 | by providing information about the necessary prerequisites for installing KubeSlice. 4 | It is essential to have a well-configured environment that fulfills the installation 5 | requirements for KubeSlice. This involves the installation of the KubeSlice Controller 6 | and registering clusters with it. This topic will explain the prerequisites in detail to 7 | help you successfully install KubeSlice. 8 | 9 | ## Required Tools 10 | To make the installation process of KubeSlice smoother and more accessible, we have listed the 11 | required command line tools below. With these tools readily available, you can easily install 12 | KubeSlice and start benefiting from its features. 13 | 14 | | Package Required | Installation Instructions | 15 | | ----------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- | 16 | | [Helm](https://helm.sh) - The Package Manager for Kubernetes | [Installing Helm](https://helm.sh/docs/intro/install/) | 17 | | [kubectl](https://kubernetes.io/docs/reference/kubectl/overview) - Kubernetes CLI | [Installing kubectl](https://kubernetes.io/docs/tasks/tools/) | 18 | | [kubectx and kubens](https://github.com/ahmetb/kubectx) - Cluster Context Switching & Namespace Assignments | [Installing kubectx & kubens](https://github.com/ahmetb/kubectx#installation) | 19 | | [kubeslice-cli ](https://github.com/kubeslice/kubeslice-cli/releases)- KubeSlice Installer Binaries | [Installing kubeslice-cli](/get-started/prerequisites/prerequisites-kubeslice-cli-install.mdx) | 20 | -------------------------------------------------------------------------------- /versioned_docs/version-1.2.0/get-started/prerequisites/prerequisites-command-line-tools.mdx: -------------------------------------------------------------------------------- 1 | # Command Line Tools 2 | This section of the documentation aims to meet the requirements for product installations 3 | by providing information about the necessary prerequisites for installing KubeSlice. 4 | It is essential to have a well-configured environment that fulfills the installation 5 | requirements for KubeSlice. This involves the installation of the KubeSlice Controller 6 | and registering clusters with it. This topic will explain the prerequisites in detail to 7 | help you successfully install KubeSlice. 8 | 9 | ## Required Tools 10 | To make the installation process of KubeSlice smoother and more accessible, we have listed the 11 | required command line tools below. With these tools readily available, you can easily install 12 | KubeSlice and start benefiting from its features. 13 | 14 | | Package Required | Installation Instructions | 15 | | ----------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- | 16 | | [Helm](https://helm.sh) - The Package Manager for Kubernetes | [Installing Helm](https://helm.sh/docs/intro/install/) | 17 | | [kubectl](https://kubernetes.io/docs/reference/kubectl/overview) - Kubernetes CLI | [Installing kubectl](https://kubernetes.io/docs/tasks/tools/) | 18 | | [kubectx and kubens](https://github.com/ahmetb/kubectx) - Cluster Context Switching & Namespace Assignments | [Installing kubectx & kubens](https://github.com/ahmetb/kubectx#installation) | 19 | | [kubeslice-cli ](https://github.com/kubeslice/kubeslice-cli/releases)- KubeSlice Installer Binaries | [Installing kubeslice-cli](/get-started/prerequisites/prerequisites-kubeslice-cli-install.mdx) | 20 | -------------------------------------------------------------------------------- /versioned_docs/version-1.3.0/get-started/prerequisites/prerequisites-command-line-tools.mdx: -------------------------------------------------------------------------------- 1 | # Command Line Tools 2 | This section of the documentation aims to meet the requirements for product installations 3 | by providing information about the necessary prerequisites for installing KubeSlice. 4 | It is essential to have a well-configured environment that fulfills the installation 5 | requirements for KubeSlice. This involves the installation of the KubeSlice Controller 6 | and registering clusters with it. This topic will explain the prerequisites in detail to 7 | help you successfully install KubeSlice. 8 | 9 | ## Required Tools 10 | To make the installation process of KubeSlice smoother and more accessible, we have listed the 11 | required command line tools below. With these tools readily available, you can easily install 12 | KubeSlice and start benefiting from its features. 13 | 14 | | Package Required | Installation Instructions | 15 | | ----------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- | 16 | | [Helm](https://helm.sh) - The Package Manager for Kubernetes | [Installing Helm](https://helm.sh/docs/intro/install/) | 17 | | [kubectl](https://kubernetes.io/docs/reference/kubectl/overview) - Kubernetes CLI | [Installing kubectl](https://kubernetes.io/docs/tasks/tools/) | 18 | | [kubectx and kubens](https://github.com/ahmetb/kubectx) - Cluster Context Switching & Namespace Assignments | [Installing kubectx & kubens](https://github.com/ahmetb/kubectx#installation) | 19 | | [kubeslice-cli ](https://github.com/kubeslice/kubeslice-cli/releases)- KubeSlice Installer Binaries | [Installing kubeslice-cli](/get-started/prerequisites/prerequisites-kubeslice-cli-install.mdx) | 20 | -------------------------------------------------------------------------------- /versioned_docs/version-1.4.0/get-started/prerequisites/prerequisites-command-line-tools.mdx: -------------------------------------------------------------------------------- 1 | # Command Line Tools 2 | This section of the documentation aims to meet the requirements for product installations 3 | by providing information about the necessary prerequisites for installing KubeSlice. 4 | It is essential to have a well-configured environment that fulfills the installation 5 | requirements for KubeSlice. This involves the installation of the KubeSlice Controller 6 | and registering clusters with it. This topic will explain the prerequisites in detail to 7 | help you successfully install KubeSlice. 8 | 9 | ## Required Tools 10 | To make the installation process of KubeSlice smoother and more accessible, we have listed the 11 | required command line tools below. With these tools readily available, you can easily install 12 | KubeSlice and start benefiting from its features. 13 | 14 | | Package Required | Installation Instructions | 15 | | ----------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- | 16 | | [Helm](https://helm.sh) - The Package Manager for Kubernetes | [Installing Helm](https://helm.sh/docs/intro/install/) | 17 | | [kubectl](https://kubernetes.io/docs/reference/kubectl/overview) - Kubernetes CLI | [Installing kubectl](https://kubernetes.io/docs/tasks/tools/) | 18 | | [kubectx and kubens](https://github.com/ahmetb/kubectx) - Cluster Context Switching & Namespace Assignments | [Installing kubectx & kubens](https://github.com/ahmetb/kubectx#installation) | 19 | | [kubeslice-cli ](https://github.com/kubeslice/kubeslice-cli/releases)- KubeSlice Installer Binaries | [Installing kubeslice-cli](/get-started/prerequisites/prerequisites-kubeslice-cli-install.mdx) | 20 | -------------------------------------------------------------------------------- /versioned_docs/version-1.0.0/release-notes/release-notes-for-kubeslice-oss-1.0.0.mdx: -------------------------------------------------------------------------------- 1 | # Release Notes for KubeSlice OSS 1.0.0 2 | 3 | *Release date: 31st May 2023* 4 | 5 | KubeSlice is a ***cloud-independent*** platform that combines network, application, Kubernetes, and deployment services 6 | in a framework to accelerate application deployment in a multi-cluster and multi-tenant environment. KubeSlice achieves this 7 | by creating logical application ***slice*** boundaries that enable seamless communication between pods and services across 8 | clusters, clouds, edges, and data centers. 9 | 10 | We continue to add new features and enhancements to KubeSlice. 11 | 12 | ## What's New 13 | These release notes describe the new changes and enhancements in this version. 14 | 15 | ### Worker Operator-generated Events 16 | The Worker Operator generates events in the `kubeslice-system` namespace. The events can 17 | be retrieved using the corresponding command. 18 | For more information, see [the Worker Operator events](/versioned_docs/version-1.0.0/install-kubeslice/yaml/events/yaml-events-worker-events.mdx). 19 | 20 | ### KubeSlice Metrics 21 | KubeSlice now records custom metrics that helps in monitoring the slice, and other KubeSlice 22 | components. These Prometheus metrics can be configured as alerts using the alert manager. 23 | For more information, see [KubeSlice metrics](/versioned_docs/version-1.0.0/install-kubeslice/yaml/metrics/yaml-metrics-controller-metrics.mdx). 24 | 25 | ### Event Integration on Slack 26 | KubeSlice-generated events can be integrated on slack to track them on a separate application workspace. 27 | 28 | For more information, see [integrate KubeSlice-generated events on Slack](/versioned_docs/version-1.0.0/add-ons/add-ons-slack-events.mdx). 29 | 30 | ### Metric-based Alerts Integration with Slack 31 | KubeSlice metric-based alerts can be integrated with Slack for brownfield and greenfield Prometheus deployments. 32 | This integration facilitates tracking the metric-based alerts on a dedicated Slack channel. 33 | For more information, see [integrate alerts with Slack](/versioned_docs/version-1.0.0/add-ons/add-ons-slack-metrics.mdx). -------------------------------------------------------------------------------- /versioned_docs/version-1.1.0/release-notes/release-notes-for-kubeslice-oss-1.0.0.mdx: -------------------------------------------------------------------------------- 1 | # Release Notes for KubeSlice OSS 1.0.0 2 | 3 | *Release date: 31st May 2023* 4 | 5 | KubeSlice is a ***cloud-independent*** platform that combines network, application, Kubernetes, and deployment services 6 | in a framework to accelerate application deployment in a multi-cluster and multi-tenant environment. KubeSlice achieves this 7 | by creating logical application ***slice*** boundaries that enable seamless communication between pods and services across 8 | clusters, clouds, edges, and data centers. 9 | 10 | We continue to add new features and enhancements to KubeSlice. 11 | 12 | ## What's New 13 | These release notes describe the new changes and enhancements in this version. 14 | 15 | ### Worker Operator-generated Events 16 | The Worker Operator generates events in the `kubeslice-system` namespace. The events can 17 | be retrieved using the corresponding command. 18 | For more information, see [the Worker Operator events](/versioned_docs/version-1.0.0/install-kubeslice/yaml/events/yaml-events-controller-events.mdx). 19 | 20 | ### KubeSlice Metrics 21 | KubeSlice now records custom metrics that helps in monitoring the slice, and other KubeSlice 22 | components. These Prometheus metrics can be configured as alerts using the alert manager. 23 | For more information, see [KubeSlice metrics](/versioned_docs/version-1.0.0/install-kubeslice/yaml/metrics/yaml-metrics-controller-metrics.mdx). 24 | 25 | ### Event Integration on Slack 26 | KubeSlice-generated events can be integrated on slack to track them on a separate application workspace. 27 | 28 | For more information, see [integrate KubeSlice-generated events on Slack](/versioned_docs/version-1.1.0/add-ons/add-ons-slack-events.mdx). 29 | 30 | ### Metric-based Alerts Integration with Slack 31 | KubeSlice metric-based alerts can be integrated with Slack for brownfield and greenfield Prometheus deployments. 32 | This integration facilitates tracking the metric-based alerts on a dedicated Slack channel. 33 | For more information, see [integrate alerts with Slack](/versioned_docs/version-1.1.0/add-ons/add-ons-slack-metrics.mdx). -------------------------------------------------------------------------------- /versioned_docs/version-1.2.0/release-notes/release-notes-for-kubeslice-oss-1.0.0.mdx: -------------------------------------------------------------------------------- 1 | # Release Notes for KubeSlice OSS 1.0.0 2 | 3 | *Release date: 31st May 2023* 4 | 5 | KubeSlice is a ***cloud-independent*** platform that combines network, application, Kubernetes, and deployment services 6 | in a framework to accelerate application deployment in a multi-cluster and multi-tenant environment. KubeSlice achieves this 7 | by creating logical application ***slice*** boundaries that enable seamless communication between pods and services across 8 | clusters, clouds, edges, and data centers. 9 | 10 | We continue to add new features and enhancements to KubeSlice. 11 | 12 | ## What's New 13 | These release notes describe the new changes and enhancements in this version. 14 | 15 | ### Worker Operator-generated Events 16 | The Worker Operator generates events in the `kubeslice-system` namespace. The events can 17 | be retrieved using the corresponding command. 18 | For more information, see [the Worker Operator events](/versioned_docs/version-1.2.0/install-kubeslice/yaml/events/yaml-events-controller-events.mdx). 19 | 20 | ### KubeSlice Metrics 21 | KubeSlice now records custom metrics that helps in monitoring the slice, and other KubeSlice 22 | components. These Prometheus metrics can be configured as alerts using the alert manager. 23 | For more information, see [KubeSlice metrics](/versioned_docs/version-1.2.0/install-kubeslice/yaml/metrics/yaml-metrics-controller-metrics.mdx). 24 | 25 | ### Event Integration on Slack 26 | KubeSlice-generated events can be integrated on slack to track them on a separate application workspace. 27 | 28 | For more information, see [integrate KubeSlice-generated events on Slack](/versioned_docs/version-1.2.0/add-ons/add-ons-slack-events.mdx). 29 | 30 | ### Metric-based Alerts Integration with Slack 31 | KubeSlice metric-based alerts can be integrated with Slack for brownfield and greenfield Prometheus deployments. 32 | This integration facilitates tracking the metric-based alerts on a dedicated Slack channel. 33 | For more information, see [integrate alerts with Slack](/versioned_docs/version-1.2.0/add-ons/add-ons-slack-metrics.mdx). -------------------------------------------------------------------------------- /versioned_docs/version-1.3.0/release-notes/release-notes-for-kubeslice-oss-1.0.0.mdx: -------------------------------------------------------------------------------- 1 | # Release Notes for KubeSlice OSS 1.0.0 2 | 3 | *Release date: 31st May 2023* 4 | 5 | KubeSlice is a ***cloud-independent*** platform that combines network, application, Kubernetes, and deployment services 6 | in a framework to accelerate application deployment in a multi-cluster and multi-tenant environment. KubeSlice achieves this 7 | by creating logical application ***slice*** boundaries that enable seamless communication between pods and services across 8 | clusters, clouds, edges, and data centers. 9 | 10 | We continue to add new features and enhancements to KubeSlice. 11 | 12 | ## What's New 13 | These release notes describe the new changes and enhancements in this version. 14 | 15 | ### Worker Operator-generated Events 16 | The Worker Operator generates events in the `kubeslice-system` namespace. The events can 17 | be retrieved using the corresponding command. 18 | For more information, see [the Worker Operator events](/versioned_docs/version-1.3.0/install-kubeslice/yaml/events/yaml-events-controller-events.mdx). 19 | 20 | ### KubeSlice Metrics 21 | KubeSlice now records custom metrics that helps in monitoring the slice, and other KubeSlice 22 | components. These Prometheus metrics can be configured as alerts using the alert manager. 23 | For more information, see [KubeSlice metrics](/versioned_docs/version-1.3.0/install-kubeslice/yaml/metrics/yaml-metrics-controller-metrics.mdx). 24 | 25 | ### Event Integration on Slack 26 | KubeSlice-generated events can be integrated on slack to track them on a separate application workspace. 27 | 28 | For more information, see [integrate KubeSlice-generated events on Slack](/versioned_docs/version-1.3.0/add-ons/add-ons-slack-events.mdx). 29 | 30 | ### Metric-based Alerts Integration with Slack 31 | KubeSlice metric-based alerts can be integrated with Slack for brownfield and greenfield Prometheus deployments. 32 | This integration facilitates tracking the metric-based alerts on a dedicated Slack channel. 33 | For more information, see [integrate alerts with Slack](/versioned_docs/version-1.3.0/add-ons/add-ons-slack-metrics.mdx). --------------------------------------------------------------------------------