profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/bhpratt/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.

IBM-Cloud/docs 140

IBM Cloud product documentation.

ibm-cloud-docs/containers 37

IBM Bluemix Container Service documentation

ibm-cloud-docs/cli 16

Documentation for the IBM Cloud CLI

bhpratt/schematics 0

Terraform and Schematics templates for IBM Cloud Kubernetes Service

issue commentibm-cloud-docs/containers

Debug / Verbose logging on IKS community ingress nginx controller

In the meantime, you may be able to use: https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/configmap/#error-log-level

bhairavi25

comment created time in a day

issue commentibm-cloud-docs/containers

Debug / Verbose logging on IKS community ingress nginx controller

Hi there - Currently there's not a way to do this with the ibm-ingress-deploy-config configmap doe the customizable deployment, but it is something I request of the dev team. I've put in an issue for them and can keep you updated.

bhairavi25

comment created time in a day

issue commentibm-cloud-docs/openshift

Min 9 worker nodes for HA

Hi, thank you for the feedback. The HA requirement that is specified in the docs is the most highly available, cost-efficient set up to receive full HA coverage under the SLA terms. This set up might exceed the minimum HA requirements for some workloads, but the level of availability that you set up for your cluster impacts your coverage under the IBM Cloud HA service level agreement terms. You can review the SLA terms here: https://cloud.ibm.com/docs/overview?topic=overview-slas

BartBogaert

comment created time in a day

issue closedibm-cloud-docs/openshift

Min 9 worker nodes for HA

According to the documentation for a HA the setup is : "with a total of at least 9 worker nodes, three worker nodes per zone that are evenly spread across three zones."

Sorry, this is not acceptable, in case your workload can be run on 1 worker node there is no reason to have at least 3 per zone

More correct would be that the sum of 2 zones out of 3 must be able to run the entire workload, so in case 1 zone goes down the workload remains available at expected performance.

closed time in a day

BartBogaert

push eventibm-cloud-docs/containers

cfsdocs

commit sha 85c22d5681b09c9afa9aa3e25ba77cdbbef28eb4

Rachael Graham: Merge pull request #6836 from alchemy-containers/rlg-firewall

view details

cfsdocs

commit sha 4f672df6c495f5fb8366986f37a273cac6240332

Rachael Graham: Merge pull request #6841 from alchemy-containers/rlg-ingress

view details

cfsdocs

commit sha 82c810e2bc80203e6526da0b8c0a4bddb44d677e

Marissa Treible: Merge pull request #6823 from alchemy-containers/mlt-pxbackup

view details

cfsdocs

commit sha 445f3cb7c9948a39cac7fe6343e1fc6cb65cc906

NADINE SPIES: Merge pull request #6846 from alchemy-containers/format-fixes

view details

cfsdocs

commit sha 44f141187aa187a0740d9f84fe06c1cf14c1cb01

Marissa Treible: Merge pull request #6845 from alchemy-containers/armada-update

view details

cfsdocs

commit sha 83fab2c201027791c28419161d0cb934a4158d8e

Rachael Graham: Merge pull request #6849 from alchemy-containers/rlg-nlb

view details

Marissa Treible

commit sha 9e5a76b04d72eaca8a52b8788c33816e6200e8b4

Merge pull request #362 from cloud-docs/next-prod-push Next prod push

view details

push time in 3 days

push eventibm-cloud-docs/openshift

cfsdocs

commit sha 7bf39ba26bd5f8eb2fd30f4448b9d9e423c2de5a

Rachael Graham: Merge pull request #6836 from alchemy-containers/rlg-firewall

view details

cfsdocs

commit sha 08ea0855a26f5c9f657ce4f18c36577d892909ab

Marissa Treible: Merge pull request #6823 from alchemy-containers/mlt-pxbackup

view details

cfsdocs

commit sha 258f4c08f0136dc1d41148be54a79b9b8cdebd60

NADINE SPIES: Merge pull request #6846 from alchemy-containers/format-fixes

view details

cfsdocs

commit sha d66058877679dd939aa278777e3ef1f505dd6bca

Marissa Treible: Merge pull request #6845 from alchemy-containers/armada-update

view details

cfsdocs

commit sha db73d7cc57bf248a3ebbbb8add7a75713290012e

Rachael Graham: Merge pull request #6849 from alchemy-containers/rlg-nlb

view details

Marissa Treible

commit sha 205ef69f280704bb73636cb6acc8b5a25a46593d

Merge pull request #283 from cloud-docs/next-prod-push Next prod push

view details

push time in 3 days

push eventIBM-Cloud/kube-samples

Laszlo Janosi

commit sha 8e62170e48a8561fa5414d9d9354d8d55a38d713

Add Akamai GTM Firewall Rules

view details

Laszlo Janosi

commit sha 4efe77a6f9d99e88a4f2ccd9209fad40a2e8c14c

add Akamai documentation link

view details

Laszlo Janosi

commit sha 3fccf7b26e66a6856423818419378e35735a52d9

Update akamai/gtm-liveness-test/README.md Co-authored-by: Rachael Graham <rachael.graham@ibm.com>

view details

Rachael Graham

commit sha d5a27264695234e76be8fb3ff5723fab04368c83

Merge pull request #133 from janosi/akamai-config Add Akamai GTM Firewall Rules

view details

push time in 3 days

PR merged IBM-Cloud/kube-samples

Add Akamai GTM Firewall Rules

Add akamai/gtm-firewall-rules/README.md to the repo. The new file contains the actual list of CIDRs from which Akamai GTM can execute liveness tests.

+93 -0

0 comment

1 changed file

janosi

pr closed time in 3 days

push eventibm-cloud-docs/RegistryImages

Sue Graham

commit sha 5122fadae24dc3d48f4bb438c192f3d079194c2c

Update index-ibmliberty.md https://github.ibm.com/alchemy-registry/documentation/issues/1207

view details

Sue Graham

commit sha 41dcd229d7a1424011bb98aad4ed8355449cfde5

Merge pull request #197 from cloud-docs/sue-graham-patch-60 Update index-ibmliberty.md

view details

push time in 4 days

Pull request review commentIBM-Cloud/kube-samples

Add Akamai GTM Firewall Rules

+# Akamai GTM Firewall Rules++You may have a firewall located in front of the servers on which you want GTM to perform liveness tests. To permit liveness tests, your firewalls must have entries added to their Access Control Lists (ACLs).++This document lists the IP addresses of all systems that might need to access your servers. If you have an ACL, make sure that you enter all of the systems listed here into your ACL.
To secure your IBM Cloud Kubernetes Service or Red Hat OpenShift on IBM Cloud cluster, you might use [Calico pre-DNAT network policies](https://cloud.ibm.com/docs/containers?topic=containers-network_policies), [VPC security groups](https://cloud.ibm.com/docs/containers?topic=containers-vpc-network-policy#security_groups), [VPC access control lists (ACLs)](https://cloud.ibm.com/docs/containers?topic=containers-vpc-network-policy#acls), or another custom firewall solution to block incoming traffic to Ingress or router services.

To ensure that the Kubernetes or OpenShift control plane can check the health of your ALBs or routers, you must allow inbound access from the following Akamai addresses and ports.
janosi

comment created time in 4 days

issue closedibm-cloud-docs/containers

Content needs to be changed(The storage-class field must be an empty string)

From below mentioned document:

https://cloud.ibm.com/docs/containers?topic=containers-file_storage#existing_file

Step 2: Creating a persistent volume (PV) and a matching persistent volume claim (PVC)

The storage-class field must be an empty string.----"must "This seems incorrect

Sometimes we may need to configure the storageClassName on our own. The statement needs to be generic for both providing value for storageClassName and for " " string.

closed time in 5 days

sivamtkr1102

issue commentibm-cloud-docs/containers

Content needs to be changed(The storage-class field must be an empty string)

@sivamtkr1102 Thanks for the feedback. The section you have linked to here - https://cloud.ibm.com/docs/containers?topic=containers-file_storage#existing_file is specifically for static provisioning with an existing NFS.

In the case of static provisioning, when you create your PVC, all of the configuration details like capacity and accessMode, etc must match your existing PV so that the provisioner can map to the existing disk. If the storage class field is not an empty string, or if any of the configuration details in your PVC do not match your existing PV, then a new PV is dynamically provisioned.

If you want to create a customized storage class that you can use to dynamically provision volumes, you can find the steps and example customized storage classes here - https://cloud.ibm.com/docs/containers?topic=containers-file_storage#file_custom_storageclass

sivamtkr1102

comment created time in 5 days

delete branch IBM-Cloud/kube-samples

delete branch : rlg-tugboat118

delete time in 5 days

push eventIBM-Cloud/kube-samples

Rachael-Graham

commit sha 6c164ceabaedb56f6bd8276d5c2a52184739a179

public

view details

Rachael-Graham

commit sha ac471fc718458e341250daffbb319dc42e51983e

private

view details

Rachael-Graham

commit sha 77970a6b02db4ef64f04f2c91daea6ef22fce639

Review

view details

Rachael-Graham

commit sha 097c0ab21c9f8efae16c350346db777cb1da31db

Missed 1 ip

view details

Rachael Graham

commit sha cddc3fb6ab84cb9cbaa6fba2569a125900f930e9

Merge pull request #132 from IBM-Cloud/rlg-tugboat118 Tugboat118 in dal10, 11, 13

view details

push time in 5 days

PR merged IBM-Cloud/kube-samples

Tugboat118 in dal10, 11, 13

internal: https://github.ibm.com/alchemy-containers/documentation/issues/6706

+24 -0

0 comment

4 changed files

Rachael-Graham

pr closed time in 5 days

Pull request review commentIBM-Cloud/kube-samples

Tugboat118 in dal10, 11, 13

 spec:       - 166.9.17.37/32       - 166.9.17.39/32       - 166.9.48.171/32+      - 166.9.48.175/32       - 166.9.48.124/32       - 166.9.48.50/32       - 166.9.48.76/32       - 166.9.51.16/32       - 166.9.51.54/32       - 166.9.51.74/32       - 166.9.51.106/32+      - 166.9.51.104/32       - 166.9.58.11/32       - 166.9.58.16/32       - 166.9.58.65/32       - 166.9.58.104/32+      - 166.9.58.170/32+      - 166.9.59.7/32

🤦

Rachael-Graham

comment created time in 5 days

push eventIBM-Cloud/kube-samples

Rachael-Graham

commit sha 097c0ab21c9f8efae16c350346db777cb1da31db

Missed 1 ip

view details

push time in 5 days

Pull request review commentIBM-Cloud/kube-samples

Tugboat118 in dal10, 11, 13

 spec:       - 166.9.17.37/32       - 166.9.17.39/32       - 166.9.48.171/32+      - 166.9.48.175/32       - 166.9.48.124/32       - 166.9.48.50/32       - 166.9.48.76/32       - 166.9.51.16/32       - 166.9.51.54/32       - 166.9.51.74/32       - 166.9.51.106/32+      - 166.9.51.104/32       - 166.9.58.11/32       - 166.9.58.16/32       - 166.9.58.65/32       - 166.9.58.104/32+      - 166.9.58.170/32+      - 166.9.59.7/32

I think this one, 166.9.59.7 still needs to be removed (it was removed from the other 3 places)

Rachael-Graham

comment created time in 5 days

PR opened IBM-Cloud/kube-samples

Add Akamai GTM Firewall Rules

Add akamai/gtm-firewall-rules/README.md to the repo. The new file contains the actual list of CIDRs from which Akamai GTM can execute liveness tests.

+91 -0

0 comment

1 changed file

pr created time in 5 days

push eventIBM-Cloud/kube-samples

Rachael-Graham

commit sha 77970a6b02db4ef64f04f2c91daea6ef22fce639

Review

view details

push time in 5 days

Pull request review commentIBM-Cloud/kube-samples

Tugboat118 in dal10, 11, 13

 spec:       - 166.9.51.54/32       - 166.9.51.74/32       - 166.9.51.106/32+      - 166.9.51.107/32

These private IPs throughout the PR aren't correct, they should be the ones that resolve the three individual hostnames that the workers use: c118-1-1.private.us-south.containers.cloud.ibm.com: 166.9.48.175 c118-2-1.private.us-south.containers.cloud.ibm.com: 166.9.51.104 c118-3-1.private.us-south.containers.cloud.ibm.com: 166.9.58.170

Rachael-Graham

comment created time in 7 days

push eventibm-cloud-docs/containers

cfsdocs

commit sha f222e37f32caf7aeb37f95c74255138f66d1ae53

Rachael Graham: Fixes (#6824)

view details

cfsdocs

commit sha fc5ce3388ad7829146f3f8839219dea48bc15963

NADINE SPIES: Merge pull request #6829 from alchemy-containers/dependency-update

view details

cfsdocs

commit sha 6b2a0b9d1fe8bfd2697794edde887c8dc1be2a19

Art Berger: Updating benchmark results for ROKS 4.6 (#6793)

view details

cfsdocs

commit sha 68297bffa3b4adaeee51644adcb1fcc75f5b75b7

Art Berger: Removing IKS and ROKS specific TS from the conref subfolders (#6837)

view details

cfsdocs

commit sha fc824fc36cb2d71f73830bb3e2f1bc5da163d938

Derek Poindexter: Merge pull request #6839 from alchemy-containers/link

view details

cfsdocs

commit sha e8ecf170b770ec1cb7ead5c2ec2d0aa35475fda0

Art Berger: Fixes branch (#6838)

view details

Art Berger

commit sha a95814d4707d81d36d2d20238db25cff1f8de33f

Merge pull request #360 from cloud-docs/next-prod-push Next prod push

view details

push time in 8 days

push eventibm-cloud-docs/openshift

cfsdocs

commit sha 3d8d5a42fbc83ff166cc00d607cf0277ae49df3e

Rachael Graham: Fixes (#6824)

view details

cfsdocs

commit sha 020884d4cfcffda9f2f6653fa1fef4a7c020a829

NADINE SPIES: Merge pull request #6829 from alchemy-containers/dependency-update

view details

cfsdocs

commit sha 6566b0e35b0a98e81d485732cd587a48925935da

Art Berger: Updating benchmark results for ROKS 4.6 (#6793)

view details

cfsdocs

commit sha 52ea7d49ed07f127369ada1a76efccd74f92b099

Art Berger: Removing IKS and ROKS specific TS from the conref subfolders (#6837)

view details

cfsdocs

commit sha 253cd8e232dfae4045690d2873d92e5e1d4d1bc9

Art Berger: Fixes branch (#6838)

view details

Art Berger

commit sha fd896703f11b5040c52bb6d741977565bff133e6

Merge pull request #281 from cloud-docs/next-prod-push Next prod push

view details

push time in 8 days

PR opened IBM-Cloud/kube-samples

Tugboat118 in dal10, 11, 13

internal: https://github.ibm.com/alchemy-containers/documentation/issues/6706

+24 -0

0 comment

4 changed files

pr created time in 8 days

push eventIBM-Cloud/kube-samples

Rachael-Graham

commit sha ac471fc718458e341250daffbb319dc42e51983e

private

view details

push time in 8 days

create barnchIBM-Cloud/kube-samples

branch : rlg-tugboat118

created branch time in 8 days

push eventibm-cloud-docs/containers

cfsdocs

commit sha b0153ad16d21f6bd3d12df0b9e3c6d30fe07bbe2

Rachael Graham: Merge pull request #6786 from alchemy-containers/rlg-istio

view details

cfsdocs

commit sha 7c6922f3167df11f4cf8123b7ed943b6770335e6

Rachael Graham: Merge pull request #6819 from alchemy-containers/rlg-calico

view details

Art Berger

commit sha eea587a733d3c6df9087273ec3d6d35c5452fcb5

Merge pull request #359 from cloud-docs/next-prod-push Next prod push

view details

push time in 9 days

push eventibm-cloud-docs/openshift

cfsdocs

commit sha 85b12138d98303ac113813b33c6aee5259205c59

Rachael Graham: Merge pull request #6786 from alchemy-containers/rlg-istio

view details

cfsdocs

commit sha f3be32414c5a1ee3fa240f30b07709291d1088ec

Rachael Graham: Merge pull request #6819 from alchemy-containers/rlg-calico

view details

cfsdocs

commit sha f5f711c529b3c03569eae59097d82791814f3482

Derek Poindexter: Merge pull request #6825 from alchemy-containers/ocs-configmap-fix

view details

Art Berger

commit sha 7c0651c895b628356a81dc30b9da1345ba9a02a0

Merge pull request #280 from cloud-docs/next-prod-push Next prod push

view details

push time in 9 days

delete branch IBM-Cloud/kube-samples

delete branch : pod-cidr-public

delete time in 10 days

push eventIBM-Cloud/kube-samples

Brad Behle

commit sha 69a87dcc3a0712c7c52509637bd9e22a7a3d37b2

Need to add a rule to public policies for pod cidr (#131) * Need to add a rule to public policies for pod cidr Due to a Calico bug fixed here: https://github.com/projectcalico/felix/pull/2582 we need to add the pod cidr to an allow egress rule, so that hosts can connect to k8s cluster IP services. * Changes due to review comments

view details

push time in 10 days