profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/jgarcows/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.

bsanaei/notifications 0

Simple extension for IBM DevOps Services to provide basic notification support

jgarcows/container_deployer 0

Extension to IBM DevOps Services for IBM Container Service

jgarcows/deployscripts 0

Deployment scripts for IBM Container Service. Used as example scripts in the Pipeline to aid in continuous deployment of an application

jgarcows/docker_builder 0

Set of scripts to extend the IBM Pipeline Service with Docker Build capabiliites

delete branch IBM-Cloud/gp-nodejs-sample

delete branch : dependabot/npm_and_yarn/lodash-4.17.19

delete time in 2 days

PR closed IBM-Cloud/gp-nodejs-sample

Bump lodash from 4.17.14 to 4.17.19 dependencies

Bumps lodash from 4.17.14 to 4.17.19. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/lodash/lodash/releases">lodash's releases</a>.</em></p> <blockquote> <h2>4.17.16</h2> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/lodash/lodash/commit/d7fbc52ee0466a6d248f047b5d5c3e6d1e099056"><code>d7fbc52</code></a> Bump to v4.17.19</li> <li><a href="https://github.com/lodash/lodash/commit/2e1c0f22f425e9c013815b2cd7c2ebd51f49a8d6"><code>2e1c0f2</code></a> Add npm-package</li> <li><a href="https://github.com/lodash/lodash/commit/1b6c282299f4e0271f932b466c67f0f822aa308e"><code>1b6c282</code></a> Bump to v4.17.18</li> <li><a href="https://github.com/lodash/lodash/commit/a370ac81408de2da77a82b3c4b61a01a3b9c2fac"><code>a370ac8</code></a> Bump to v4.17.17</li> <li><a href="https://github.com/lodash/lodash/commit/1144918f3578a84fcc4986da9b806e63a6175cbb"><code>1144918</code></a> Rebuild lodash and docs</li> <li><a href="https://github.com/lodash/lodash/commit/3a3b0fd339c2109563f7e8167dc95265ed82ef3e"><code>3a3b0fd</code></a> Bump to v4.17.16</li> <li><a href="https://github.com/lodash/lodash/commit/c84fe82760fb2d3e03a63379b297a1cc1a2fce12"><code>c84fe82</code></a> fix(zipObjectDeep): prototype pollution (<a href="https://github-redirect.dependabot.com/lodash/lodash/issues/4759">#4759</a>)</li> <li><a href="https://github.com/lodash/lodash/commit/e7b28ea6cb17b4ca021e7c9d66218c8c89782f32"><code>e7b28ea</code></a> Sanitize sourceURL so it cannot affect evaled code (<a href="https://github-redirect.dependabot.com/lodash/lodash/issues/4518">#4518</a>)</li> <li><a href="https://github.com/lodash/lodash/commit/0cec225778d4ac26c2bac95031ecc92a94f08bbb"><code>0cec225</code></a> Fix lodash.isEqual for circular references (<a href="https://github-redirect.dependabot.com/lodash/lodash/issues/4320">#4320</a>) (<a href="https://github-redirect.dependabot.com/lodash/lodash/issues/4515">#4515</a>)</li> <li><a href="https://github.com/lodash/lodash/commit/94c3a8133cb4fcdb50db72b4fd14dd884b195cd5"><code>94c3a81</code></a> Document matches* shorthands for over* methods (<a href="https://github-redirect.dependabot.com/lodash/lodash/issues/4510">#4510</a>) (<a href="https://github-redirect.dependabot.com/lodash/lodash/issues/4514">#4514</a>)</li> <li>Additional commits viewable in <a href="https://github.com/lodash/lodash/compare/4.17.14...4.17.19">compare view</a></li> </ul> </details> <details> <summary>Maintainer changes</summary> <p>This version was pushed to npm by <a href="https://www.npmjs.com/~mathias">mathias</a>, a new releaser for lodash since your current version.</p> </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>

+5 -5

1 comment

2 changed files

dependabot[bot]

pr closed time in 2 days

pull request commentIBM-Cloud/gp-nodejs-sample

Bump lodash from 4.17.14 to 4.17.19

Superseded by #28.

dependabot[bot]

comment created time in 2 days

PR opened IBM-Cloud/gp-nodejs-sample

Bump lodash from 4.17.14 to 4.17.21

Bumps lodash from 4.17.14 to 4.17.21. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/lodash/lodash/commit/f299b52f39486275a9e6483b60a410e06520c538"><code>f299b52</code></a> Bump to v4.17.21</li> <li><a href="https://github.com/lodash/lodash/commit/c4847ebe7d14540bb28a8b932a9ce1b9ecbfee1a"><code>c4847eb</code></a> Improve performance of <code>toNumber</code>, <code>trim</code> and <code>trimEnd</code> on large input strings</li> <li><a href="https://github.com/lodash/lodash/commit/3469357cff396a26c363f8c1b5a91dde28ba4b1c"><code>3469357</code></a> Prevent command injection through <code>_.template</code>'s <code>variable</code> option</li> <li><a href="https://github.com/lodash/lodash/commit/ded9bc66583ed0b4e3b7dc906206d40757b4a90a"><code>ded9bc6</code></a> Bump to v4.17.20.</li> <li><a href="https://github.com/lodash/lodash/commit/63150ef7645ac07961b63a86490f419f356429aa"><code>63150ef</code></a> Documentation fixes.</li> <li><a href="https://github.com/lodash/lodash/commit/00f0f62a979d2f5fa0287c06eae70cf9a62d8794"><code>00f0f62</code></a> test.js: Remove trailing comma.</li> <li><a href="https://github.com/lodash/lodash/commit/846e434c7a5b5692c55ebf5715ed677b70a32389"><code>846e434</code></a> Temporarily use a custom fork of <code>lodash-cli</code>.</li> <li><a href="https://github.com/lodash/lodash/commit/5d046f39cbd27f573914768e3b36eeefcc4f1229"><code>5d046f3</code></a> Re-enable Travis tests on <code>4.17</code> branch.</li> <li><a href="https://github.com/lodash/lodash/commit/aa816b36d402a1ad9385142ce7188f17dae514fd"><code>aa816b3</code></a> Remove <code>/npm-package</code>.</li> <li><a href="https://github.com/lodash/lodash/commit/d7fbc52ee0466a6d248f047b5d5c3e6d1e099056"><code>d7fbc52</code></a> Bump to v4.17.19</li> <li>Additional commits viewable in <a href="https://github.com/lodash/lodash/compare/4.17.14...4.17.21">compare view</a></li> </ul> </details> <details> <summary>Maintainer changes</summary> <p>This version was pushed to npm by <a href="https://www.npmjs.com/~bnjmnt4n">bnjmnt4n</a>, a new releaser for lodash since your current version.</p> </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>

+5 -5

0 comment

2 changed files

pr created time in 2 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

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

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

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

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

PR merged IBM-Cloud/kube-samples

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.

+72 -0

0 comment

10 changed files

bradbehle

pr closed time in 10 days

push eventIBM-Cloud/kube-samples

Brad Behle

commit sha 2aacbb1e771f287a383b641242b801584038ddc8

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.

view details

Brad Behle

commit sha 13cc7dc5121c82d339dfce139bd7d69c911441e6

Changes due to review comments

view details

push time in 10 days

Pull request review commentIBM-Cloud/kube-samples

Need to add a rule to public policies for pod cidr

 The Calico policies are organized by region. Choose the directory for the region  > NOTE: The policies in the ca-tor directory are meant for use with the Toronto multizone location. For the Toronto single zone location, use the policies in the us-east directory instead. +## Deployment Notes++If your cluster uses a custom pod subnet (something other than 172.30.0.0/16), including if the cluster is a VPC+cluster (which doesn't use the standard pod subnet by default), then before applying the policies, change the+instances of 172.30.0.0/16 in these policies to the pod subnet for this cluster

I made these changes

bradbehle

comment created time in 10 days

Pull request review commentIBM-Cloud/kube-samples

Need to add a rule to public policies for pod cidr

 The Calico policies are organized by region. Choose the directory for the region  > NOTE: The policies in the ca-tor directory are meant for use with the Toronto multizone location. For the Toronto single zone location, use the policies in the us-east directory instead. +## Deployment Notes++If your cluster uses a custom pod subnet (something other than 172.30.0.0/16), including if the cluster is a VPC+cluster (which doesn't use the standard pod subnet by default), then before applying the policies, change the+instances of 172.30.0.0/16 in these policies to the pod subnet for this cluster

I made these changes

bradbehle

comment created time in 10 days

Pull request review commentIBM-Cloud/kube-samples

Need to add a rule to public policies for pod cidr

 spec:       nets:       - 172.20.0.0/24     protocol: TCP+  - action: Allow+    destination:+      nets:+      # Allows communication from host to a cluster IP service.  This is need in these public+      # policies for now due to https://github.com/projectcalico/felix/pull/2582+      # If you specified a custom pod subnet when you created the cluster, use that CIDR instead.

I added this to ca-tor, and made the suggested modifications, except I did keep the reference to "these public policies" since this rule is already in the private policies and makes sense there. It is needed in these public policies (where it doesn't really make sense) due to the bug I reference

bradbehle

comment created time in 10 days

Pull request review commentIBM-Cloud/kube-samples

Need to add a rule to public policies for pod cidr

 spec:       nets:       - 172.20.0.0/24     protocol: TCP+  - action: Allow+    destination:+      nets:+      # Allows communication from host to a cluster IP service.  This is need in these public+      # policies for now due to https://github.com/projectcalico/felix/pull/2582+      # If you specified a custom pod subnet when you created the cluster, use that CIDR instead.

and same ^ throughout

bradbehle

comment created time in 10 days

Pull request review commentIBM-Cloud/kube-samples

Need to add a rule to public policies for pod cidr

 The Calico policies are organized by region. Choose the directory for the region  > NOTE: The policies in the ca-tor directory are meant for use with the Toronto multizone location. For the Toronto single zone location, use the policies in the us-east directory instead. +## Deployment Notes++If your cluster uses a custom pod subnet (something other than 172.30.0.0/16), including if the cluster is a VPC+cluster (which doesn't use the standard pod subnet by default), then before applying the policies, change the+instances of 172.30.0.0/16 in these policies to the pod subnet for this cluster
These policies specify worker node egress to `172.30.0.0/16` as the default pod subnet. If you specified a custom pod 
subnet when you created a classic cluster, or if you use a VPC cluster (which doesn't use the standard pod subnet by 
default), you must edit the `allow-ibm-ports-public.yaml` policy to change `172.30.0.0/16` to the pod subnet CIDR for 
this cluster instead. To find your cluster's pod subnet, run `ibmcloud ks cluster get -c <cluster_name_or_ID>`.
bradbehle

comment created time in 10 days

Pull request review commentIBM-Cloud/kube-samples

Need to add a rule to public policies for pod cidr

 The Calico policies are organized by region. Choose the directory for the region  > NOTE: The policies in the ca-tor directory are meant for use with the Toronto multizone location. For the Toronto single zone location, use the policies in the us-east directory instead. +## Deployment Notes++If your cluster uses a custom pod subnet (something other than 172.30.0.0/16), including if the cluster is a VPC+cluster (which doesn't use the standard pod subnet by default), then before applying the policies, change the+instances of 172.30.0.0/16 in these policies to the pod subnet for this cluster

maybe:

These policies specify worker node egress to `172.30.0.0/16` as the default pod subnet. If you specified a custom pod 
subnet when you created a classic cluster, or if you use a VPC cluster (which doesn't use the standard pod subnet by 
default), you must edit the `allow-all-workers-private.yaml` policy to change `172.30.0.0/16` to the pod subnet CIDR for 
this cluster instead. To find your cluster's pod subnet, run `ibmcloud ks cluster get -c <cluster_name_or_ID>`.
bradbehle

comment created time in 10 days