Skip to content

resolve: replicas issue and add network testing section #1388

New issue

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

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

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jan 31, 2025

Conversation

SuyogShinde942
Copy link
Contributor

No description provided.


## Network Isolation Testing

This section verifies that the network policies are correctly isolating HelloWorldService instances.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

correctly isolating application instances.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We will use HelloWorldService as an example.

$ eval $(minikube docker-env)
```

#### Refer for main readme for installing the kubeplus operator and plugings
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Refer main README ...

- **Ping/HTTP Test from `hs1` to `hs2`:**

```bash
$ HELLOWORLD_POD_HS1=$(kubectl get pods -n hs1 --kubeconfig=consumer.conf -o jsonpath='{.items[0].metadata.name}')
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here we can just use provider.conf


```bash
$ HELLOWORLD_POD_HS1=$(kubectl get pods -n hs1 --kubeconfig=consumer.conf -o jsonpath='{.items[0].metadata.name}')
$ kubectl exec -it $HELLOWORLD_POD_HS1 -n hs1 --kubeconfig=consumer.conf -- curl <hs2-app-endpoint>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

provider.conf

- **Ping/HTTP Test from `hs2` to `hs1`:**

```bash
$ HELLOWORLD_POD_HS2=$(kubectl get pods -n hs2 --kubeconfig=consumer.conf -o jsonpath='{.items[0].metadata.name}')
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

provider.conf


```bash
$ HELLOWORLD_POD_HS2=$(kubectl get pods -n hs2 --kubeconfig=consumer.conf -o jsonpath='{.items[0].metadata.name}')
$ kubectl exec -it $HELLOWORLD_POD_HS2 -n hs2 --kubeconfig=consumer.conf -- curl <hs1-app-endpoint>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

provider.conf

### As Consumer

```bash
$ kubectl delete -f hs1-no-replicas.yaml --kubeconfig=consumer.conf
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can get rid of the Consumer section. Merge these with the steps from the provider section. Then merge the two sections and get rid of "As Consumer" and "As Provider" sub-sections.

@@ -11,7 +11,7 @@ spec:
version: v1alpha1
plural: helloworldservices
# URL of the Helm chart that contains Kubernetes resources that represent a workflow.
chartURL: https://github.com/cloud-ark/operatorcharts/blob/master/hello-world-chart-0.0.2.tgz?raw=true
chartURL: https://github.com/cloud-ark/kubeplus/blob/master/examples/multitenancy/hello-world/hello-world-chart-0.0.3.tgz?raw=true
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants