profile
viewpoint
Michael Tanenbaum tbaums @d2iq NYC Sales Engineer @d2iq

startedaltair-viz/altair

started time in 12 hours

push eventtbaums/konvoy-kudo-studio

tbaums

commit sha e25260b9cf3cda4839795ec78fc6e03a3fb06fa5

rounded mouse pixel position

view details

tbaums

commit sha ebdf5e605836d64dab9c68a98bf1e618f4d2b1bb

added example kf notebook to show results from C*

view details

push time in a day

push eventtbaums/konvoy-kudo-studio

tbaums

commit sha 463670fc5d8040c14bd5e500c85e9e28233a098f

add error handling and clean up warnings

view details

push time in a day

push eventtbaums/konvoy-kudo-studio

tbaums

commit sha b76f0fa928a195672be5d5fff40fcb7f9e59f1cc

add apply command for cassandra connector

view details

push time in a day

push eventtbaums/konvoy-kudo-studio

tbaums

commit sha 1f6803b1c96f441619928ccc73423661609872d8

data piped to Cassandra working

view details

push time in a day

issue openedkudobuilder/operators

Cassandra Grafana dashboard link broken

Link to Grafana dashboard yields 404.

Line 74 - https://github.com/kudobuilder/operators/blob/master/repository/cassandra/3.11/docs/monitoring.md

created time in 2 days

PR opened d2l-ai/d2l-en

fix typo

later --> latter

Description of changes:

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

+1 -1

0 comment

1 changed file

pr created time in 10 days

push eventtbaums/d2l-en

Michael Tanenbaum

commit sha 81a29ece99798bfa6620c5dc39c1286f5762d5ae

fix typo later --> latter

view details

push time in 10 days

push eventtbaums/d2l-en

Michael Tanenbaum

commit sha bc30e86f9c6e5a24d6c5af338aa8f8b5db27f650

fix typo later --> latter

view details

push time in 10 days

Pull request review commentmesosphere/dcos-docs-site

D2KF Technical Preview release docs

+---+layout: kommander-docs-landing.pug+navigationTitle: D2iQ Kubeflow+title: D2iQ Kubeflow+menuWeight: 1+menus: ['d2kf-header']+---++Welcome to D2iQ Kubeflow

update to d2kf

akirillov

comment created time in 14 days

pull request commentmesosphere/dcos-docs-site

D2KF Technical Preview release docs

@akirillov - comments inline.

akirillov

comment created time in 14 days

Pull request review commentmesosphere/dcos-docs-site

D2KF Technical Preview release docs

+---+layout: layout.pug+navigationTitle: manage users+title: Manage Users and Permissions+menuWeight: 10+excerpt: Manage Kubeflow users and permissions+beta: false+enterprise: false+---++# Manage Kubeflow Users and Permissions++Prerequisites: +- Administrative access to a properly configured Konvoy cluster via `kubectl`++D2KF comes with a set of predefined Kubernetes `ClusterRoles` designed to simplify the workflow of Kubeflow administrators who want to onboard new team members.++Because a single Kubeflow user needs to interact with Kubernetes resources across both the Kubeflow namespace and their own Kubeflow `Profile` namespace, D2iQ recommends appropriately permissioned `ClusterRole` objects. As with all matters regarding security, we encourage you to thoroughly review permissions set by our predefined `ClusterRoles` in conjunction with your security team.++## Kubeflow Predefined `ClusterRoles`++Predefined `ClusterRoles` for Kubeflow tenants are as follows:++1. `kubeflow-admin` - Appropriate for administrators of the Kubeflow instance.+1. `kubeflow-edit` - Appropriate for data scientists, data engineers, MLOps engineers, or other Kubeflow tenants.+1. `kubeflow-view` - Appropriate for those who should have view-only access to the Kubeflow instance.++For a chart of the permissions granted to each `ClusterRole`, see the [Permissions Charts](#permissions-charts).++## Assigning Permissions to Kubeflow Users++_NB: The following tutorial assumes you have already connected an OIDC provider to your Konvoy cluster via Konvoy's built-in Dex integration. If you have not yet done so, review the documentation [here](https://docs.d2iq.com/ksphere/konvoy/latest/security/external-idps/) before proceeding._++### Adding Permissions for a Kubeflow Administrator     ++#### Step 1 - Create the `ClusterRoleBinding` YAML manifest++In your terminal shell, run:++```bash+cat << EOF > add-kubeflow-admin.yaml                                        +apiVersion: rbac.authorization.k8s.io/v1+kind: ClusterRoleBinding+metadata:+  name: "<name of user>"+roleRef:+  apiGroup: rbac.authorization.k8s.io+  kind: ClusterRole+  name: kubeflow-admin+subjects:+- apiGroup: rbac.authorization.k8s.io+  kind: User+  name: "<Email of user>"+EOF++```++#### Step 2 - Edit `add-kubeflow-admin.yaml` with details for the new user++Edit the `metadata.name` to the name of the user you want to add. ++**Note** This name should be globally unique across your Konvoy cluster, otherwise you may overwrite another user's permissions.++Edit the `subjects.apiGroup.name` to match the email address associated with the user's OIDC account.+++#### Step 3 - Apply `add-kubeflow-admin.yaml` to your Konvoy cluster++In your terminal shell, run:++`kubectl apply -f add-kubeflow-admin.yaml` ++Your output should look similar to this:++```bash+kubectl apply -f add-kubeflow-admin.yaml                              ++clusterrolebinding.rbac.authorization.k8s.io/<name of user> created+```++### Adding Permissions for a Kubeflow User++#### Step 1 - Create the `ClusterRoleBinding` YAML manifest++In your terminal shell, run:++```bash+cat << EOF > add-kubeflow-user.yaml                                        +apiVersion: rbac.authorization.k8s.io/v1+kind: ClusterRoleBinding+metadata:+  name: "<name of user>"+roleRef:+  apiGroup: rbac.authorization.k8s.io+  kind: ClusterRole+  name: kubeflow-edit+subjects:+- apiGroup: rbac.authorization.k8s.io+  kind: User+  name: "<Email of user>"+EOF++```++#### Step 2 - Edit `add-kubeflow-user.yaml` with details for the new user++Edit the `metadata.name` to the name of the user you want to add. ++**Note** This name should be globally unique across your Konvoy cluster, otherwise you may overwrite another user's permissions.++Edit `subjects.apiGroup.name` to match the email address associated with the user's OIDC account.+++#### Step 3 - Apply `add-kubeflow-user.yaml` to your Konvoy cluster++In your terminal shell, run: ++`kubectl apply -f add-kubeflow-user.yaml` ++Your output should look similar to this:++```bash+kubectl apply -f add-kubeflow-user.yaml                              ++clusterrolebinding.rbac.authorization.k8s.io/<name of user> created+```++# Permissions Charts

these charts look odd to me. @akirillov - can you look over them and make sure that k9s is outputting the permissions correctly here?

akirillov

comment created time in 14 days

Pull request review commentmesosphere/dcos-docs-site

D2KF Technical Preview release docs

+---+layout: layout.pug+navigationTitle: manage users+title: Manage Users and Permissions+menuWeight: 10+excerpt: Manage Kubeflow users and permissions+beta: false+enterprise: false+---++# Manage Kubeflow Users and Permissions++Prerequisites: +- Administrative access to a properly configured Konvoy cluster via `kubectl`++D2KF comes with a set of predefined Kubernetes `ClusterRoles` designed to simplify the workflow of Kubeflow administrators who want to onboard new team members.++Because a single Kubeflow user needs to interact with Kubernetes resources across both the Kubeflow namespace and their own Kubeflow `Profile` namespace, D2iQ recommends appropriately permissioned `ClusterRole` objects. As with all matters regarding security, we encourage you to thoroughly review permissions set by our predefined `ClusterRoles` in conjunction with your security team.++## Kubeflow Predefined `ClusterRoles`++Predefined `ClusterRoles` for Kubeflow tenants are as follows:++1. `kubeflow-admin` - Appropriate for administrators of the Kubeflow instance.+1. `kubeflow-edit` - Appropriate for data scientists, data engineers, MLOps engineers, or other Kubeflow tenants.+1. `kubeflow-view` - Appropriate for those who should have view-only access to the Kubeflow instance.++For a chart of the permissions granted to each `ClusterRole`, see the [Permissions Charts](#permissions-charts).++## Assigning Permissions to Kubeflow Users++_NB: The following tutorial assumes you have already connected an OIDC provider to your Konvoy cluster via Konvoy's built-in Dex integration. If you have not yet done so, review the documentation [here](https://docs.d2iq.com/ksphere/konvoy/latest/security/external-idps/) before proceeding._++### Adding Permissions for a Kubeflow Administrator     ++#### Step 1 - Create the `ClusterRoleBinding` YAML manifest++In your terminal shell, run:++```bash+cat << EOF > add-kubeflow-admin.yaml                                        +apiVersion: rbac.authorization.k8s.io/v1+kind: ClusterRoleBinding+metadata:+  name: "<name of user>"+roleRef:+  apiGroup: rbac.authorization.k8s.io+  kind: ClusterRole+  name: kubeflow-admin+subjects:+- apiGroup: rbac.authorization.k8s.io+  kind: User+  name: "<Email of user>"+EOF++```++#### Step 2 - Edit `add-kubeflow-admin.yaml` with details for the new user++Edit the `metadata.name` to the name of the user you want to add. ++**Note** This name should be globally unique across your Konvoy cluster, otherwise you may overwrite another user's permissions.++Edit the `subjects.apiGroup.name` to match the email address associated with the user's OIDC account.+++#### Step 3 - Apply `add-kubeflow-admin.yaml` to your Konvoy cluster++In your terminal shell, run:++`kubectl apply -f add-kubeflow-admin.yaml` ++Your output should look similar to this:++```bash+kubectl apply -f add-kubeflow-admin.yaml                              ++clusterrolebinding.rbac.authorization.k8s.io/<name of user> created+```++### Adding Permissions for a Kubeflow User++#### Step 1 - Create the `ClusterRoleBinding` YAML manifest++In your terminal shell, run:++```bash+cat << EOF > add-kubeflow-user.yaml                                        +apiVersion: rbac.authorization.k8s.io/v1+kind: ClusterRoleBinding+metadata:+  name: "<name of user>"+roleRef:+  apiGroup: rbac.authorization.k8s.io+  kind: ClusterRole+  name: kubeflow-edit+subjects:+- apiGroup: rbac.authorization.k8s.io+  kind: User+  name: "<Email of user>"+EOF++```++#### Step 2 - Edit `add-kubeflow-user.yaml` with details for the new user++Edit the `metadata.name` to the name of the user you want to add. ++**Note** This name should be globally unique across your Konvoy cluster, otherwise you may overwrite another user's permissions.

missing ":" after "Note"

akirillov

comment created time in 14 days

Pull request review commentmesosphere/dcos-docs-site

D2KF Technical Preview release docs

+---+layout: layout.pug+navigationTitle: manage users+title: Manage Users and Permissions+menuWeight: 10+excerpt: Manage Kubeflow users and permissions+beta: false+enterprise: false+---++# Manage Kubeflow Users and Permissions++Prerequisites: +- Administrative access to a properly configured Konvoy cluster via `kubectl`++D2KF comes with a set of predefined Kubernetes `ClusterRoles` designed to simplify the workflow of Kubeflow administrators who want to onboard new team members.++Because a single Kubeflow user needs to interact with Kubernetes resources across both the Kubeflow namespace and their own Kubeflow `Profile` namespace, D2iQ recommends appropriately permissioned `ClusterRole` objects. As with all matters regarding security, we encourage you to thoroughly review permissions set by our predefined `ClusterRoles` in conjunction with your security team.++## Kubeflow Predefined `ClusterRoles`++Predefined `ClusterRoles` for Kubeflow tenants are as follows:++1. `kubeflow-admin` - Appropriate for administrators of the Kubeflow instance.+1. `kubeflow-edit` - Appropriate for data scientists, data engineers, MLOps engineers, or other Kubeflow tenants.+1. `kubeflow-view` - Appropriate for those who should have view-only access to the Kubeflow instance.++For a chart of the permissions granted to each `ClusterRole`, see the [Permissions Charts](#permissions-charts).++## Assigning Permissions to Kubeflow Users++_NB: The following tutorial assumes you have already connected an OIDC provider to your Konvoy cluster via Konvoy's built-in Dex integration. If you have not yet done so, review the documentation [here](https://docs.d2iq.com/ksphere/konvoy/latest/security/external-idps/) before proceeding._++### Adding Permissions for a Kubeflow Administrator     ++#### Step 1 - Create the `ClusterRoleBinding` YAML manifest++In your terminal shell, run:++```bash+cat << EOF > add-kubeflow-admin.yaml                                        +apiVersion: rbac.authorization.k8s.io/v1+kind: ClusterRoleBinding+metadata:+  name: "<name of user>"+roleRef:+  apiGroup: rbac.authorization.k8s.io+  kind: ClusterRole+  name: kubeflow-admin+subjects:+- apiGroup: rbac.authorization.k8s.io+  kind: User+  name: "<Email of user>"+EOF++```++#### Step 2 - Edit `add-kubeflow-admin.yaml` with details for the new user++Edit the `metadata.name` to the name of the user you want to add. ++**Note** This name should be globally unique across your Konvoy cluster, otherwise you may overwrite another user's permissions.

missing ":" after "Note"

akirillov

comment created time in 14 days

Pull request review commentmesosphere/dcos-docs-site

D2KF Technical Preview release docs

+---+layout: layout.pug+navigationTitle: Manage Secrets+title: Manage Secrets+menuWeight: 5+excerpt: Distribute a sensible configuration securely+beta: false+enterprise: false+---++# Overview ++Enabling data scientists and machine learning engineers to utilize 3rd-party services that live outside Kubeflow (or even outside the Konvoy cluster on which Kubeflow resides), requires a simple and secure mechanism for distributing usernames, passwords, and other sensitive data. Luckily, Kubeflow administrators can share specific credentials with specific Kubeflow platform tenants in a granular fashion, while tenants can access that sensitive data without exposing it in plain text.++## Manage Secrets with Kubeflow ++To expose a Kubernetes Secret to Jupyter notebooks launched from Kubeflow, ensure you have Kubeflow administrator privileges, then go to the Kubernetes cluster that houses the Kubeflow tenant's workspace namespace, create a secret, and deploy a `PodDefault` object.++Then, when a Kubeflow tenant launches a Jupyter notebook, they can select any secrets (or ConfigMaps, environment variables, etc.) configured via PodDefaults for the Kubeflow namespace in the launcher configuration window. The Kubeflow MutatingWebhookConfiguration (pre-configured with Kubeflow and requiring no further adjustment by Kubeflow administrators) ensures that any notebooks launched in the tenant's namespace are injected with that data per the `PodDefault` specification.++## Manage Secrets Tutorial++### Step 1 - Confirm the Kubeflow tenant namespace name++Each Kubeflow tenant receives their own namespace on the shared Konvoy cluster. Although the Kubeflow UI will suggest that the tenant use a namespace name that matches the login from the OIDC provider attached to Konvoy, there is no *requirement* that the tenant do so. ++As a result, Kubeflow administrators must confirm the name selected by the tenant upon first login. ++Furthermore, as `PodDefault` objects are namespaced, and the tenant's namespace is only created _after_ logging in for the first time, administrators must wait until the tenant logs in for the first time before continuing with the steps below.++The following output shows a Kubeflow tenant who has logged in and named their namespace "alice":++```bash+kubectl get namespaces                                                                  ++NAME              STATUS   AGE+alice             Active   54m+cert-manager      Active   107m+default           Active   108m+istio-system      Active   104m+knative-serving   Active   104m+kube-node-lease   Active   108m+kube-public       Active   108m+kube-system       Active   108m+kubeaddons        Active   107m+kubeflow          Active   66m+kudo-system       Active   64m+```++### Step 2 - Create a secret in Kubeflow tenant's namespace++Next, create a `Secret` in the "alice" namespace.++```bash+kubectl create secret generic -n alice test-secret --from-literal=foo=bar  +secret/test-secret created+```++### Step 3 - Create `PodDefault` in Kubeflow tenant's namespace++With the command below, create a `PodDefault` object that injects the test-secret `Secret` created in step 2 into any new notebook created that requires it.++```bash+cat << EOF | kubectl apply -f -+apiVersion: "kubeflow.org/v1alpha1"+kind: PodDefault+metadata:+  name: test-secret+  namespace: alice+spec:+ selector:+  matchLabels:+    test-secret: "true"+ desc: "test-secret"+ volumeMounts:+ - name: secret-volume+   mountPath: /secret/test-secret+ volumes:+ - name: secret-volume+   secret:+    secretName: test-secret+EOF+++poddefault.kubeflow.org/test-secret created+```++### Step 4 - Launch Jupyter notebook and select test-secret from the Configurations drop-down ++After successfully deploying the `PodDefault`, select the test-secret for injection into the new Jupyter notebook.++![notebook-configs](/kudo-kubeflow/docs/site/resources/images/notebook-configurations-select.png)

img link broken

akirillov

comment created time in 14 days

Pull request review commentmesosphere/dcos-docs-site

D2KF Technical Preview release docs

+---+layout: layout.pug+navigationTitle: Introducing D2KF+title: Introducing D2KF+excerpt: Deploy and manage machine learning models with ease+menuWeight: 1+---+D2KF is a cloud-native suite of best-of-breed open-source technologies that allow data scientists to extract value from data immediately by providing a familiar environment for development and all the technologies needed to deploy and scale models in production, while keeping your valuable data safe. D2KF solves a key problem that enterprises face: How to get a return on your expensive AI investments? Going from a prototype to a deployment is often hard, but it does not have to be thanks to D2KF.++D2iQ's D2KF leverages our expertise in Kubernetes, so companies can run their machine learning workloads anywhere: in the cloud, on premise, locally, or in hybrid environments.+D2KF is an opinionated distribution based on Kubeflow: everything you need to train, deploy, and scale models is packaged and tested, so you can rest assured that it works out of the box. With its fast and easy setup from [Kommander](https://docs.d2iq.com/ksphere/kommander/), your data scientists can be up and running in no time!++## D2KF's Features and Benefits++| **Features**                                      | **Benefits**                                                 |+| ------------------------------------------------- | ------------------------------------------------------------ |+| Out-of-the-box integration of Spark and Horovod   | No need to install additional libraries to create data pipelines or train Spark ML models on multiple CPUs or GPUs |+| Fully tested pre-baked notebook images            | A familiar environment that has been fully tested and integrates with all the shared resources (CPUs, GPUs) and data access controls needed to build and share models as a team |+ |

formatting of table appears to be broken.

akirillov

comment created time in 14 days

PR opened d2l-ai/d2l-en

parallel structure correction

Description of changes:

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

+1 -1

0 comment

1 changed file

pr created time in 17 days

push eventtbaums/d2l-en

Michael Tanenbaum

commit sha fa588c2253bca566f47dfa8f3e8ff1014abf04b9

parallel structure correction

view details

push time in 17 days

PR opened d2l-ai/d2l-en

grammar correction

Description of changes:

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

+1 -1

0 comment

1 changed file

pr created time in 17 days

push eventtbaums/d2l-en

Michael Tanenbaum

commit sha aeae0d9554c4ce415f895f7d58c967055ab456ff

grammar correction

view details

push time in 17 days

push eventtbaums/d2l-en

Michael Tanenbaum

commit sha 162020c30aaa5536b4f0c1e8c80a6b1cf0ebfc27

correct typo

view details

push time in 17 days

PR opened d2l-ai/d2l-en

correct typo

Description of changes:

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

+1 -1

0 comment

1 changed file

pr created time in 17 days

PR opened d2l-ai/d2l-en

correct typo

Description of changes:

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

+1 -1

0 comment

1 changed file

pr created time in 17 days

push eventtbaums/d2l-en

Michael Tanenbaum

commit sha 13c45bb80472030c1325ba25142424b047482a7a

correct typo

view details

push time in 17 days

PR opened d2l-ai/d2l-en

Fix typo

Correct grammar error

Description of changes:

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

+1 -1

0 comment

1 changed file

pr created time in 17 days

push eventtbaums/d2l-en

Michael Tanenbaum

commit sha cb6153e6b62b6cfb0b64f634599e8917ef80c41c

Fix typo Correct grammar error

view details

push time in 17 days

Pull request review commentmesosphere/dcos-docs-site

Add procedure to attach EKS cluster to Kommander.

+---+layout: layout.pug+navigationTitle: Attach Amazon EKS Cluster to Kommander+title: Attach Amazon EKS Cluster to Kommander+menuWeight: 7+excerpt: Attach an existing EKS cluster to Kommander+beta: true +enterprise: false+---++You can attach any existing Kubernetes clusters to Kommander, then use it to examine and manage those clusters later. The following procedure shows how to attach an existing Amazon Elastic Kubernetes Service (EKS) cluster to Kommander. ++## Before you begin ++This procedure requires the following items and configurations:++- A fully configured and running Amazon [EKS](https://aws.amazon.com/eks/) cluster.+- Konvoy v1.5.0-beta.0 or above, [installed and configured](https://docs.d2iq.com/ksphere/konvoy/1.5.0-beta/install/) for your Amazon EKS cluster, on your machine.+- Kommander v1.0.1-beta.1 or above, [installed and configured](https://docs.d2iq.com/ksphere/kommander/1.1.0-beta/install/) on your machine.++<p class="message--note"><strong>NOTE: </strong>This procedure assumes you have at least one existing and spun up Amazon EKS cluster. Refer to the Amazon EKS [website](https://aws.amazon.com/eks/) for setup and configuration information.</p>++## Attach Amazon EKS Clusters to Kommander++1. Ensure you are connected to your first EKS cluster. Enter the following commands:++    ```bash+    kubectl config get-contexts+    kubectl config use-context <context for first eks cluster>+    ```++1. Confirm `kubectl` can access the EKS cluster.  ++    ```bash+    kubectl get no+    ```+    +1. Create a service account for Kommander on your EKS cluster.++    ```bash+    kubectl -n kube-system create serviceaccount kommander-cluster-admin+    ```+    +1. Configure your `kommander-cluster-admin` service account to have `cluster-admin` permissions. Enter the following commands:++    ```yaml+    cat << EOF | kubectl apply -f -+    apiVersion: rbac.authorization.k8s.io/v1beta1+    kind: ClusterRoleBinding+    metadata:+      name: kommander-cluster-admin+    roleRef:+      apiGroup: rbac.authorization.k8s.io+      kind: ClusterRole+      name: cluster-admin+    subjects:+    - kind: ServiceAccount+      name: kommander-cluster-admin+      namespace: kube-system+    EOF+    ```++1. Create a kubeconfig file compatible with the Kommander UI. Enter these commands to set the following environment variables:

correct. this whole rigamarole is due to the fact that the default kubeconfig file used/created by EKS is not compatible with the kommander UI.

russurquhart1

comment created time in 17 days

Pull request review commentmesosphere/dcos-docs-site

Add procedure to attach EKS cluster to Kommander.

+---+layout: layout.pug+navigationTitle: Attach Amazon EKS Cluster to Kommander+title: Attach Amazon EKS Cluster to Kommander+menuWeight: 7+excerpt: Attach an existing EKS cluster to Kommander+beta: true +enterprise: false+---++You can attach any existing Kubernetes clusters to Kommander, then use it to examine and manage those clusters later. The following procedure shows how to attach an existing Amazon Elastic Kubernetes Service (EKS) cluster to Kommander. ++## Before you begin ++This procedure requires the following items and configurations:++- A fully configured and running Amazon [EKS](https://aws.amazon.com/eks/) cluster.+- Konvoy v1.5.0-beta.0 or above, [installed and configured](https://docs.d2iq.com/ksphere/konvoy/1.5.0-beta/install/) for your Amazon EKS cluster, on your machine.+- Kommander v1.0.1-beta.1 or above, [installed and configured](https://docs.d2iq.com/ksphere/kommander/1.1.0-beta/install/) on your machine.++<p class="message--note"><strong>NOTE: </strong>This procedure assumes you have at least one existing and spun up Amazon EKS cluster. Refer to the Amazon EKS [website](https://aws.amazon.com/eks/) for setup and configuration information.</p>++## Attach Amazon EKS Clusters to Kommander++1. Ensure you are connected to your first EKS cluster. Enter the following commands:

good catch @cmastr . @russurquhart1 - should remove the word 'first'.

russurquhart1

comment created time in 17 days

Pull request review commentmesosphere/dcos-docs-site

Add procedure to attach EKS cluster to Kommander.

+---+layout: layout.pug+navigationTitle: Attach Amazon EKS Cluster to Kommander+title: Attach Amazon EKS Cluster to Kommander+menuWeight: 7+excerpt: Attach an existing EKS cluster to Kommander+beta: true +enterprise: false+---++You can attach existing Kubernetes clusters to Kommander. After attaching the cluster, you can use Kommander to examine and manage this cluster. The following procedure shows how to attach an existing Amazon Elastic Kubernetes Service (EKS) cluster to Kommander. ++## Before you begin ++This procedure requires the following items and configurations:++- A fully configured and running Amazon [EKS](https://aws.amazon.com/eks/) cluster+- Konvoy v1.5.0-beta.0 or above, [installed and configured](https://docs.d2iq.com/ksphere/konvoy/1.5.0-beta/install/) for your Amazon EKS cluster, on your machine.+- Kommander v1.0.1-beta.1 or above, [installed and configured](https://docs.d2iq.com/ksphere/kommander/1.1.0-beta/install/) on your machine.++<p class="message--note"><strong>NOTE: </strong>This procedure assumes you have an existing and spun up Amazon EKS cluster(s). Refer to the Amazon EKS [website](https://aws.amazon.com/eks/) for setup and configuration information. </p>++## Attach Amazon EKS Clusters to Kommander++1. Ensure you are connected to your first EKS cluster. Enter the following commands:++    ```bash+    kubectl config get-contexts+    kubectl config use-context <context for first eks cluster>+    ```++1. Confirm `kubectl` can access the EKS cluster.  ++    ```bash+    kubectl get no+    ```+    +1. Create a service account for Kommander on your EKS cluster.++    ```bash+    kubectl -n kube-system create serviceaccount kommander-cluster-admin+    ```+    +1. Configure your `kommander-cluster-admin` service account to have `cluster-admin` permissions. Enter the following commands:++    ```yaml+    cat << EOF | kubectl apply -f -+    apiVersion: rbac.authorization.k8s.io/v1beta1+    kind: ClusterRoleBinding+    metadata:+      name: kommander-cluster-admin+    roleRef:+      apiGroup: rbac.authorization.k8s.io+      kind: ClusterRole+      name: cluster-admin+    subjects:+    - kind: ServiceAccount+      name: kommander-cluster-admin+      namespace: kube-system+    EOF+    ```++1. Create a kubeconfig file compatible with the Kommander UI. Enter these commands to set the following environment variables:++    ```bash+    export USER_TOKEN_NAME=$(kubectl -n kube-system get serviceaccount kommander-cluster-admin -o=jsonpath='{.secrets[0].name}')+    export USER_TOKEN_VALUE=$(kubectl -n kube-system get secret/${USER_TOKEN_NAME} -o=go-template='{{.data.token}}' | base64 --decode)+    export CURRENT_CONTEXT=$(kubectl config current-context)+    export CURRENT_CLUSTER=$(kubectl config view --raw -o=go-template='{{range .contexts}}{{if eq .name "'''${CURRENT_CONTEXT}'''"}}{{ index .context "cluster" }}{{end}}{{end}}')+    export CLUSTER_CA=$(kubectl config view --raw -o=go-template='{{range .clusters}}{{if eq .name "'''${CURRENT_CLUSTER}'''"}}{{ index .cluster "certificate-authority-data" }}{{end}}{{ end }}')+    export CLUSTER_SERVER=$(kubectl config view --raw -o=go-template='{{range .clusters}}{{if eq .name "'''${CURRENT_CLUSTER}'''"}}{{ .cluster.server }}{{end}}{{ end }}')+    ```++1. Confirm these variables have been set correctly:++    ```bash+    env | grep CLUSTER+    ```++1. Create a new kubeconfig file to use in the Kommander UI. Enter the following commands:++    ```bash+    cat << EOF > kommander-cluster-admin-config+    apiVersion: v1+    kind: Config+    current-context: ${CURRENT_CONTEXT}+    contexts:+    - name: ${CURRENT_CONTEXT}+      context:+        cluster: ${CURRENT_CONTEXT}+        user: kommander-cluster-admin+        namespace: kube-system+    clusters:+    - name: ${CURRENT_CONTEXT}+      cluster:+        certificate-authority-data: ${CLUSTER_CA}+        server: ${CLUSTER_SERVER}+    users:+    - name: kommander-cluster-admin+      user:+        token: ${USER_TOKEN_VALUE}+    EOF+    ```++1. Verify the kubeconfig file can access the EKS cluster.++    ```bash+    kubectl --kubeconfig $(pwd)/kommander-cluster-admin-config get all --all-namespaces+    ```++1. Copy `kommander-cluster-admin-config` to your clipboard.++    ```bash+    cat kommander-cluster-admin-config | pbcopy

you could just have them run cat kommander-cluster-admin-config and copy/paste the yaml file.

you paste the file into the kommander ui. looks like it also supports uploading the file directly.

attaching a screenshot. Screen Shot 2020-05-18 at 4 34 12 PM

russurquhart1

comment created time in 17 days

Pull request review commentmesosphere/dcos-docs-site

Add procedure to attach EKS cluster to Kommander.

+---+layout: layout.pug+navigationTitle: Attach Amazon EKS Cluster to Kommander+title: Attach Amazon EKS Cluster to Kommander+menuWeight: 7+excerpt: Attach an existing EKS cluster to Kommander+beta: true +enterprise: false+---++You can attach existing Kubernetes clusters to Kommander. After attaching the cluster, you can use Kommander to examine and manage this cluster. The following procedure shows how to attach an existing Amazon Elastic Kubernetes Service (EKS) cluster to Kommander. ++## Before you begin ++This procedure requires the following items and configurations:++- A fully configured and running Amazon [EKS](https://aws.amazon.com/eks/) cluster+- Konvoy v1.5.0-beta.0 or above, [installed and configured](https://docs.d2iq.com/ksphere/konvoy/1.5.0-beta/install/) for your Amazon EKS cluster, on your machine.+- Kommander v1.0.1-beta.1 or above, [installed and configured](https://docs.d2iq.com/ksphere/kommander/1.1.0-beta/install/) on your machine.++<p class="message--note"><strong>NOTE: </strong>This procedure assumes you have an existing and spun up Amazon EKS cluster(s). Refer to the Amazon EKS [website](https://aws.amazon.com/eks/) for setup and configuration information. </p>++## Attach Amazon EKS Clusters to Kommander++1. Ensure you are connected to your first EKS cluster. Enter the following commands:++    ```bash+    kubectl config get-contexts+    kubectl config use-context <context for first eks cluster>+    ```++1. Confirm `kubectl` can access the EKS cluster.  ++    ```bash+    kubectl get no+    ```+    +1. Create a service account for Kommander on your EKS cluster.++    ```bash+    kubectl -n kube-system create serviceaccount kommander-cluster-admin+    ```+    +1. Configure your `kommander-cluster-admin` service account to have `cluster-admin` permissions. Enter the following commands:++    ```yaml+    cat << EOF | kubectl apply -f -+    apiVersion: rbac.authorization.k8s.io/v1beta1+    kind: ClusterRoleBinding+    metadata:+      name: kommander-cluster-admin+    roleRef:+      apiGroup: rbac.authorization.k8s.io+      kind: ClusterRole+      name: cluster-admin+    subjects:+    - kind: ServiceAccount+      name: kommander-cluster-admin+      namespace: kube-system+    EOF+    ```++1. Create a kubeconfig file compatible with the Kommander UI. Enter these commands to set the following environment variables:++    ```bash+    export USER_TOKEN_NAME=$(kubectl -n kube-system get serviceaccount kommander-cluster-admin -o=jsonpath='{.secrets[0].name}')+    export USER_TOKEN_VALUE=$(kubectl -n kube-system get secret/${USER_TOKEN_NAME} -o=go-template='{{.data.token}}' | base64 --decode)+    export CURRENT_CONTEXT=$(kubectl config current-context)+    export CURRENT_CLUSTER=$(kubectl config view --raw -o=go-template='{{range .contexts}}{{if eq .name "'''${CURRENT_CONTEXT}'''"}}{{ index .context "cluster" }}{{end}}{{end}}')+    export CLUSTER_CA=$(kubectl config view --raw -o=go-template='{{range .clusters}}{{if eq .name "'''${CURRENT_CLUSTER}'''"}}{{ index .cluster "certificate-authority-data" }}{{end}}{{ end }}')+    export CLUSTER_SERVER=$(kubectl config view --raw -o=go-template='{{range .clusters}}{{if eq .name "'''${CURRENT_CLUSTER}'''"}}{{ .cluster.server }}{{end}}{{ end }}')+    ```++1. Confirm these variables have been set correctly:++    ```bash+    env | grep CLUSTER+    ```++1. Create a new kubeconfig file to use in the Kommander UI. Enter the following commands:++    ```bash+    cat << EOF > kommander-cluster-admin-config+    apiVersion: v1+    kind: Config+    current-context: ${CURRENT_CONTEXT}+    contexts:+    - name: ${CURRENT_CONTEXT}+      context:+        cluster: ${CURRENT_CONTEXT}+        user: kommander-cluster-admin+        namespace: kube-system+    clusters:+    - name: ${CURRENT_CONTEXT}+      cluster:+        certificate-authority-data: ${CLUSTER_CA}+        server: ${CLUSTER_SERVER}+    users:+    - name: kommander-cluster-admin+      user:+        token: ${USER_TOKEN_VALUE}+    EOF+    ```++1. Verify the kubeconfig file can access the EKS cluster.++    ```bash+    kubectl --kubeconfig $(pwd)/kommander-cluster-admin-config get all --all-namespaces+    ```++1. Copy `kommander-cluster-admin-config` to your clipboard.++    ```bash+    cat kommander-cluster-admin-config | pbcopy

this command will only work on MacOS. Need a linux version.

russurquhart1

comment created time in 17 days

Pull request review commentmesosphere/dcos-docs-site

Add procedure to attach EKS cluster to Kommander.

+---+layout: layout.pug+navigationTitle: Attach Amazon EKS Cluster to Kommander+title: Attach Amazon EKS Cluster to Kommander+menuWeight: 7+excerpt: Attach an existing EKS cluster to Kommander+beta: true +enterprise: false+---++You can attach existing Kubernetes clusters to Kommander. After attaching the cluster, you can use Kommander to examine and manage this cluster. The following procedure shows how to attach an existing Amazon Elastic Kubernetes Service (EKS) cluster to Kommander. ++## Before you begin ++This procedure requires the following items and configurations:++- A fully configured and running Amazon [EKS](https://aws.amazon.com/eks/) cluster

with administrative privileges.

russurquhart1

comment created time in 17 days

PR opened d2l-ai/d2l-en

Fix typo: Subject-verb agreement

Description of changes:

Fix minor typo whereby indirect object was missing resulting in subject-verb singular/plural mismatch.

I inferred from the end of the sentence the author(s) intended singular.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

+2 -2

0 comment

1 changed file

pr created time in 23 days

push eventtbaums/d2l-en

Michael Tanenbaum

commit sha 3eda360f61d8d6f833c2315ba65bdf9d226fa95a

Fix typo: Subject-verb agreement

view details

push time in 23 days

fork tbaums/d2l-en

An interactive deep learning book with code, math, and discussions, based on the NumPy interface.

https://d2l.ai

fork in 23 days

startedd2l-ai/d2l-en

started time in 23 days

push eventtbaums/konvoy-kudo-studio

Michael Tanenbaum

commit sha 2eb266b4463fda10e3a7a8460a40fa32a79aa599

Create LICENSE

view details

push time in a month

push eventtbaums/konvoy-kudo-studio

tbaums

commit sha 97c399c85c7db4229c5077a15a4df528ccb7105d

added MNIST prediction app API

view details

Michael Tanenbaum

commit sha 94a8e3e216f45136deea0f91eb9a99c942549a8c

Merge pull request #9 from tbaums/prediction-api added MNIST prediction app API

view details

push time in a month

create barnchtbaums/konvoy-kudo-studio

branch : prediction-api

created branch time in a month

issue openedkudobuilder/kudo.dev

Feedback link in kudo docs broken

<!-- Please use this template while reporting a docs bug and provide the device used to read the docs, and a link to the site that's broken plus, if useful, a screenshot. Thanks! -->

Which page is affected?:

https://kudo.dev/docs/runbooks/kafka/upgrade-kafka.html#steps

What exactly is broken?:

Link directs to https://github.com/kudobuilder/kudo.dev/edit/master/content/docs/runbooks/kafka/upgrade-kafka.md which gives a 404

Which device do you use?:

Chrome

Anything else we need to know?:

May affect other pages, too. Didn't check.

created time in a month

PR opened kudobuilder/operators

copy edits and update ZOOKEEPER_URI in examples

Fixed a few typos.

Updated ZOOKEEPER_URI in examples to match the defaults created by kk install zookeeper

+12 -12

0 comment

1 changed file

pr created time in a month

create barnchkudobuilder/operators

branch : kafka-zk-docs-patch

created branch time in a month

issue commentkudobuilder/kudo

Implement feedback link for docs on kudo.dev

My fault!

tbaums

comment created time in a month

issue closedkudobuilder/kudo

Implement feedback link for docs on kudo.dev

<!-- Please only use this template for submitting enhancement requests. Implementing your enhancement will follow the KEP process: https://github.com/kudobuilder/kudo/blob/master/keps/0001-kep-process.md -->

What would you like to be added:

AA KUDO community member and user, I want a feedback link (or other easy mechanism) on kudo.dev docs pages so that I can submit docs issues without needing to hunt around in the GH repo to find the page and the problem area.

Why is this needed:

Good docs == happy users == healthy project!

closed time in a month

tbaums

issue openedkudobuilder/kudo

Implement feedback link for docs on kudo.dev

<!-- Please only use this template for submitting enhancement requests. Implementing your enhancement will follow the KEP process: https://github.com/kudobuilder/kudo/blob/master/keps/0001-kep-process.md -->

What would you like to be added:

AA KUDO community member and user, I want a feedback link (or other easy mechanism) on kudo.dev docs pages so that I can submit docs issues without needing to hunt around in the GH repo to find the page and the problem area.

Why is this needed:

Good docs == happy users == healthy project!

created time in a month

push eventtbaums/eks-kubeflow-demo

tbaums

commit sha 89a16d972e5e21eadc3aba20f33bbadb8fb2ea21

revert to unmanaged node groups

view details

push time in a month

push eventtbaums/eks-kubeflow-demo

tbaums

commit sha 60710aaa32adb968101285b5ed4cff6330d7d557

disable istio

view details

push time in a month

push eventtbaums/k9s

tbaums

commit sha 7af00d64ecbe3172757a3d3cf5b966171ba8bb6e

logo swap

view details

push time in a month

fork tbaums/k9s

🐶 Kubernetes CLI To Manage Your Clusters In Style!

https://k9scli.io

fork in a month

push eventtbaums/eks-kubeflow-demo

tbaums

commit sha e8de61506bf7e0a0470f44c25e51b48a56571146

remove gpu workers from kommander cluster

view details

tbaums

commit sha 29b3a92add0300e5ed7c7f1ea65cc922ba8bfec0

Create custom-repo.yaml

view details

tbaums

commit sha 5db0fec842b8befd00df05bed38397ede6808369

turn off nvidia

view details

tbaums

commit sha 2c3fe7108cbebd0058bf92f2b72bc61b91991943

Create .gitignore

view details

tbaums

commit sha 2d4880e804024e0d819074a84b9bbc45df77d381

add reminder to detach clusters

view details

push time in a month

push eventtbaums/eks-kubeflow-demo

tbaums

commit sha 87f032a2a7a674cab59273872672f9f86c40208e

add gpu to cluster.yaml

view details

push time in a month

push eventtbaums/eks-kubeflow-demo

tbaums

commit sha 80404578a359ef1da051f730e3e302d5ff227996

working eks attachment instructions

view details

push time in a month

push eventtbaums/kubeaddons-demo

Michael Tanenbaum

commit sha 9a15e7af92e506d19f22d28fac3f2319a1bebf99

Update helloworld-1.yaml

view details

push time in a month

push eventtbaums/kubeaddons-demo

Michael Tanenbaum

commit sha c02acab1b83c52a1dfafaa2559157e06e247be4b

Delete helloworld-5.yaml

view details

push time in a month

push eventtbaums/kubeaddons-demo

Michael Tanenbaum

commit sha 699a7bc0ab77ecdf959c629380fffd512c3dfc09

Delete helloworld-4.yaml

view details

push time in a month

push eventtbaums/kubeaddons-demo

Michael Tanenbaum

commit sha a373b00745d0cd600387cedfd4977c7785b82bd2

Delete helloworld-3.yaml

view details

push time in a month

push eventtbaums/kubeaddons-demo

Michael Tanenbaum

commit sha 0b6cc2f798a3442e5209c3bf9c5b265d14bb5a1c

Delete helloworld-2.yaml

view details

push time in a month

pull request commentmesosphere/dcos-docs-site

Update the attach cluster to Kommander docs

Another thought - Can we profile the resource requirements of the workloads Kommander will deploy to the EKS cluster by default and warn users that (1) Kommander will deploy its stack to the cluster once attached, and (2) how much headroom they will need in their cluster to allow for that?

armandgrillet

comment created time in a month

create barnchtbaums/eks-kubeflow-demo

branch : master

created branch time in a month

created repositorytbaums/eks-kubeflow-demo

created time in a month

pull request commentmesosphere/dcos-docs-site

Update the attach cluster to Kommander docs

@armandgrillet - I think my commit fixes the problem in a reliable way. LMK your thoughts!

armandgrillet

comment created time in a month

push eventmesosphere/dcos-docs-site

tbaums

commit sha fb90f6e00b28a6e50a53750f204e8d67860e00f3

fix current-cluster / current-context mismatch

view details

push time in a month

push eventtbaums/konvoy-kudo-studio

tbaums

commit sha 4bff479c721984c53b9f741ce10c6766bea4ca41

update node-js-api to make dynamic

view details

tbaums

commit sha adca9489484df442a37bd4097543480217ae5e65

add turbo dummy actor yaml

view details

push time in a month

push eventtbaums/konvoy-kudo-studio

tbaums

commit sha 9577c05bde21703ac8212682e67d499a979a9e28

update kafka-client-api to make namespace agnostic

view details

push time in a month

push eventtbaums/konvoy-kudo-studio

tbaums

commit sha 5cb43d7aeb2ddba5299aa6fa2827433288ac9cb2

update readme to reflect azure tested

view details

tbaums

commit sha 9a77219b6c51a7a96e287fe50643329b3affcfcc

Merge branch 'master' of https://github.com/tbaums/konvoy-kudo-studio

view details

push time in a month

PR merged tbaums/konvoy-kudo-studio

Bump acorn from 7.1.0 to 7.1.1 in /svelte-ui dependencies javascript

Bumps acorn from 7.1.0 to 7.1.1. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/acornjs/acorn/commit/6d194895783b03b2a37441f01857c34302eab4c8"><code>6d19489</code></a> Mark release 7.1.1</li> <li><a href="https://github.com/acornjs/acorn/commit/793c0e569ed1158672e3a40aeed1d8518832b802"><code>793c0e5</code></a> More rigorously check surrogate pairs in regexp validator</li> <li><a href="https://github.com/acornjs/acorn/commit/b5c17877ac0511e31579ea31e7650ba1a5871e51"><code>b5c1787</code></a> Fix incorrect comment in regexp parser</li> <li><a href="https://github.com/acornjs/acorn/commit/12ae8fed7ebc5b7c894c5976575f33cf36a223cc"><code>12ae8fe</code></a> Parameterize dummy value and export <code>isDummy</code></li> <li><a href="https://github.com/acornjs/acorn/commit/fa3ad8cef0f39f5ae0cbd8be0bf65eb0a782133e"><code>fa3ad8c</code></a> Further refine acorn-walk types</li> <li><a href="https://github.com/acornjs/acorn/commit/1d5028637852c2834091739646e25dd6558ee7a8"><code>1d50286</code></a> Fix some errors in walk types</li> <li><a href="https://github.com/acornjs/acorn/commit/97801f0b5835bc93739666b3494c9b49aeb5fc1d"><code>97801f0</code></a> Mark acorn-walk 7.1.1</li> <li><a href="https://github.com/acornjs/acorn/commit/e9372c151f63fe254c7f5e7ffd7a820e34422208"><code>e9372c1</code></a> Further clean up walker types</li> <li><a href="https://github.com/acornjs/acorn/commit/de6edeb654cf665e732d822d95c97e2d2fc879bc"><code>de6edeb</code></a> Remove NarrowNode from walk.d.ts</li> <li><a href="https://github.com/acornjs/acorn/commit/1d85e7ce982a979bb5411cd00fd9156eecf952a5"><code>1d85e7c</code></a> Fix: acorn-walk type work with acorn's</li> <li>Additional commits viewable in <a href="https://github.com/acornjs/acorn/compare/7.1.0...7.1.1">compare view</a></li> </ul> </details> <br />

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

+3 -3

0 comment

1 changed file

dependabot[bot]

pr closed time in a month

push eventtbaums/konvoy-kudo-studio

dependabot[bot]

commit sha 87ef2bf67f9759d0bc8218ebf851c53b7cd05ee8

Bump acorn from 7.1.0 to 7.1.1 in /svelte-ui Bumps [acorn](https://github.com/acornjs/acorn) from 7.1.0 to 7.1.1. - [Release notes](https://github.com/acornjs/acorn/releases) - [Commits](https://github.com/acornjs/acorn/compare/7.1.0...7.1.1) Signed-off-by: dependabot[bot] <support@github.com>

view details

Michael Tanenbaum

commit sha 4ece32ee17ab79caebdf1da1db07451a21ceec3e

Merge pull request #8 from tbaums/dependabot/npm_and_yarn/svelte-ui/acorn-7.1.1 Bump acorn from 7.1.0 to 7.1.1 in /svelte-ui

view details

push time in a month

push eventtbaums/konvoy-kudo-studio

tbaums

commit sha df3590d0e4a446b98ed0e8b9db21bfd9872f0111

fix typo

view details

push time in a month

push eventtbaums/konvoy-kudo-studio

tbaums

commit sha 43604770363dbb40f2a3a858bc9f12ff71e1fc59

trim old files

view details

push time in a month

push eventtbaums/konvoy-kudo-studio

tbaums

commit sha 886469b81834a1e7682ba6f780b085508977ba98

reformat tested versions

view details

push time in a month

push eventtbaums/konvoy-kudo-studio

tbaums

commit sha 90906fe0b110f69a012b535dd08b5ba806030a16

updated to make ClusterIP discovery dynamic for kafka-client-api!

view details

push time in a month

push eventtbaums/konvoy-kudo-studio

tbaums

commit sha f79d625176c94311d12c943418fda8f1479508ff

fix links with new api folder change

view details

push time in a month

push eventtbaums/konvoy-kudo-studio

tbaums

commit sha 777f7bb23878e875f9160ec9e710c3cad221e1d1

update and improve main readme

view details

push time in a month

push eventtbaums/konvoy-kudo-studio

tbaums

commit sha bb234e20ff8ad5a62777e2e79283e066c33e21b9

add kafka and zookeeper local files

view details

push time in a month

push eventtbaums/konvoy-kudo-studio

tbaums

commit sha e54713fe77eb9bd084feb98068734c6c4ac1c558

add airgapped instructions

view details

push time in a month

push eventtbaums/konvoy-kudo-studio

tbaums

commit sha b2e0e95bdb45de42d1ccabee70d952b6c34e3d59

rename kafka-python-api folder to kafka-client-api

view details

push time in a month

more