profile
viewpoint
Josh Gavant joshgav Discover Financial Services Chicago, IL

joshgav/azure-log-processor 2

Receive and process logs from Azure resources via Event Hubs.

joshgav/azure-scripts 2

Scripts for deploying to Azure platforms.

joshgav/gdrive 2

CLI for Google Drive.

joshgav/azure-go-labs 1

Labs demonstrating how to use Go on Azure.

joshgav/chrome-remote-interface 1

Chrome Debugging Protocol interface

joshgav/diagnostics 1

Tracing Working Group

joshgav/go-sample 1

Sample app for tests.

joshgav/ApplicationInsights-node.js 0

Microsoft Application Insights SDK for node.js

joshgav/appsvc-scratch 0

scripts and tests for Azure App Service

created tagjoshgav/eventing-contrib

tagv0.11.3

Event Sources

created time in a month

pull request commentknative/eventing-contrib

support other cred providers in sqs adapter

@googlebot I signed it!

joshgav

comment created time in a month

PR opened knative/eventing-contrib

support other cred providers in sqs adapter

Background

I'd like to use the SQS adapter from awssqs/pkg/adapter with a custom credentials provider, but at the moment the adapter strictly uses a credentials file.

This PR proposes allowing the adapter to accept any AWS credentials provider, which will enable others to initialize and inject their own. It also updates the adapter container's main.go to create and use a file-based provider so that this change is transparent to current container users.

Proposed Changes

Release Note <!-- Enter your extended release note in the below block. If the PR requires additional action from users switching to the new release, include the string "action required". If no release note is required, write "NONE". -->

The SQS receive_adapter now accepts a credentials provider rather than a path to a credentials file, enabling use of alternate providers. If you use the adapter via the default cmd and container this change is transparent. If you use the adapter directly then action required: you will need to specify your file in a SharedCredentials provider and use that to initialize the adapter.
+17 -5

0 comment

2 changed files

pr created time in a month

push eventjoshgav/eventing-contrib

Josh Gavant

commit sha 85591597e3642419205828b84a6eb6ec4e4590d1

support other cred providers in sqs adapter

view details

push time in a month

push eventjoshgav/eventing-contrib

Josh Gavant

commit sha 5b34c6cbe5e0d7918e60179e7d34a486628da2c1

support other cred providers in sqs adapter

view details

push time in a month

create barnchjoshgav/eventing-contrib

branch : sqs-creds

created branch time in a month

push eventjoshgav/postgres-operator-usage

Josh Gavant

commit sha 52a9995e5ee75b8d552ceb79c32f60e5bd2546e6

add olm diagram

view details

push time in 2 months

create barnchjoshgav/postgres-operator-usage

branch : master

created branch time in 2 months

created repositoryjoshgav/postgres-operator-usage

Scripts for utilizing CrunchyData's postgres-operator in OpenShift.

created time in 2 months

issue commentbrigadecore/brigade

pods crash-loop in default OpenShift cluster

Hi @radu-matei, sure. In addition to the UID issue, OpenShift uses routes, approximately equal to ingresses but not quite, so I couldn't use the ingresses in the Brigade charts and configured my own routes instead.

All up and running now :+1: so I'll document these couple items when I have a chance and find a place to submit them here. If you all document before let me know, happy to review.

joshgav

comment created time in 3 months

startedaelsabbahy/goss

started time in 3 months

issue openedbrigadecore/brigade

pods crash-loop in default OpenShift cluster

Hi team, hope you're well! Wanted to let you know that extra configuration is required to run Brigade on OpenShift. This seems to be because the Brigade containers expect to run as a specific user/UID and OpenShift's default policy is to assign a UID of its choosing (links follow for reference).

Specifically, after I deploy the Brigade chart I have to run oc adm policy add-scc-to-group anyuid system:serviceaccounts:brigade to allow its containers to use their chosen UID (brigade is the namespace where I deployed brigade). Note that requires a cluster admin.

Assuming that config is indeed required in OpenShift it would be great to document it, and even better if you could arrange for Brigade's containers to run with arbitrary UIDs so no exceptional policy would be needed - info on that in the links. Thanks for the consideration.

If that policy isn't applied you'll see CrashLoopBackOffs for the pods and errors like the following in the logs:

kubectl logs deployment/brigade-brigade-ctrl
    W1204 20:54:32.937750       1 client_config.go:533] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
    log: exiting because of error: log: cannot create log: open /tmp/brigade-controller.brigade-brigade-ctrl-5874b54cd5-zpd2p.unknownuser.log.WARNING.20191204-205432.1: permission denied
kubectl logs deployment/brigade-brigade-api
    W1204 20:55:42.609026       1 client_config.go:533] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
    log: exiting because of error: log: cannot create log: open /tmp/brigade-api.brigade-brigade-api-696b6c89fd-cr4qd.unknownuser.log.WARNING.20191204-205542.1: permission denied
kubectl logs deployment/brigade-kashti
    2019/12/04 20:55:40 [warn] 1#1: the "user" directive makes sense only if the master process runs with super-user privileges, ignored in /etc/nginx/nginx.conf:2
    nginx: [warn] the "user" directive makes sense only if the master process runs with super-user privileges, ignored in /etc/nginx/nginx.conf:2
    2019/12/04 20:55:40 [emerg] 1#1: mkdir() "/var/cache/nginx/client_temp" failed (13: Permission denied)
    nginx: [emerg] mkdir() "/var/cache/nginx/client_temp" failed (13: Permission denied)

Links re UIDs in OpenShift:


Output of brig version:

v1.2.1

Output of kubectl version:

Client Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.3", GitCommit:"b3cbbae08ec52a7fc73d334838e18d17e8512749", GitTreeState:"clean", BuildDate:"2019-11-13T11:23:11Z", GoVersion:"go1.12.12", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"14+", GitVersion:"v1.14.6+dea7fb9", GitCommit:"dea7fb9", GitTreeState:"clean", BuildDate:"2019-11-19T17:18:37Z", GoVersion:"go1.12.12", Compiler:"gc", Platform:"linux/amd64"}

Output of oc version:

Client Version: unknown
Server Version: 4.2.8
Kubernetes Version: v1.14.6+dea7fb9

Cloud Provider/Platform (AKS, GKE, Minikube etc.):

CodeReady Containers: https://github.com/code-ready/crc

created time in 3 months

push eventjoshgav/goss

Josh Gavant

commit sha e9ade59c533c5a2257ef2688a7072f4dbb62894f

remove kgoss from published artifacts

view details

push time in 3 months

Pull request review commentaelsabbahy/goss

add "kgoss" kubectl wrapper to test containers in Kubernetes

 deploy:     - release/goss-linux-386     - release/goss-linux-arm     - extras/dgoss/dgoss+    - extras/kgoss/kgoss

No problem @aelsabbahy, I just removed that line. Makes sense not to include in a release at this point, looking forward to getting a bit more feedback.

joshgav

comment created time in 3 months

push eventjoshgav/goss

Josh Gavant

commit sha 8de4e92d5da4136628087830e55b8a1512d9f93a

remove kgoss from published artifacts

view details

push time in 3 months

pull request commentaelsabbahy/goss

add "kgoss" kubectl wrapper to test containers in Kubernetes

Hi @aelsabbahy - I think this is ready to go, LMK if you'd like anything further.

joshgav

comment created time in 3 months

issue openedkudobuilder/kudo.dev

mailing list link broken

Which page is affected?:

https://kudo.dev/community/

What exactly is broken?:

Mailing List link goes to a non-existent or private group. I receive the alert: "This group either doesn't exist, or you don't have permission to access it. If you're sure this group exists, contact the Owner of the group and ask them to give you access." Here's a screenshot:

Screen Shot 2019-11-26 at 3 18 00 PM

Which device do you use?:

Chrome browser on Mac.

created time in 3 months

startedcncf/sig-app-delivery

started time in 3 months

push eventjoshgav/goss

Josh Gavant

commit sha 1523ddcfbd7911ca42c22a844db29f5a70266a74

add kgoss kubectl wrapper

view details

push time in 3 months

pull request commentaelsabbahy/goss

add "kgoss" kubectl wrapper to test containers in Kubernetes

Updated and rebased, tests pass, ready for merge @aelsabbahy.

joshgav

comment created time in 3 months

push eventjoshgav/goss

PlusMinus0

commit sha 82972c1db7b39b0536192f8fd70faf058d7ba685

Update install.sh to use latest version (#460)

view details

Justin

commit sha 91fba64ea8663b586d8449dc872e8c2f836ef0d1

[dgoss] Use inspect instead of top in health check (#473)

view details

Hervé

commit sha b6b0d23444e32a0b251c553e8080917d0addc88e

Also display container logs when using the wait feature (#415)

view details

Matthew Taylor

commit sha 8bb5f3501c3b784b1117d95699db015f75fff233

Clarify process check usage (#486)

view details

Ahmed Elsabbahy

commit sha 9d1d4db3d84e4691138c6abef2cc258da5b51321

Fix failing integration test due to google DNS name change (#491)

view details

Ahmed Elsabbahy

commit sha 7bbd54d676f87886230cd69eb5b2521331178d8b

Clarify user check is a local /etc/passwd check, fixes #482 (#492)

view details

racarvalho1987

commit sha e799071c38849b0860f55b05f94d0ae356281465

Issue 493 Change permission from tmp_dir so less privileged user can … (#494) * Issue 493 Change permission from tmp_dir so less privileged user can run goss Include a chmod 644 to set read permission from any user that runs the goss tests * Execute chmod after copy the yaml files to tmp_dir folder * Change file permission from specific files Instead of change file permissions recursively declare the chmod for each file. Avoind change the permission of goss binary file.

view details

Ahmed Elsabbahy

commit sha a4a501a4a755c882dd5ab920df3b9c6bb27d9779

Fix dgoss bug with docker inspect

view details

Ahmed Elsabbahy

commit sha 9dddd816d63f7e7217a1021f4e1c5ee0a50f0512

Fix dgoss bug with docker inspect

view details

Ahmed Elsabbahy

commit sha 4aa1330180a7630d30bc51ab2301ed6cbb627f98

Fix command ID (#495)

view details

David Campbell

commit sha aa0fc088b0e9a56272bcb0b404372d8d81607b28

Added request headers to http tests (#496) * Added request headers to http tests * Pinning go 1.13 * Pinning Travis version of go to 1.13 * Bumping the count of tests being run * Updating the docs to reflect new request headers

view details

Ahmed Elsabbahy

commit sha ee6ae7f2f66071fb26cf32c942c81128294417b7

Pr 296 (#498) * Add validation for http header * Add http headers: [] to goss-expected tests. * Add http header test in goss-shared.yaml. * Update expected test counts.

view details

Ahmed Elsabbahy

commit sha c78568d2306ea080a45de560fa59b615bd744a5a

Use httpbin for header test. Do not include header by default. Update docs. (#500)

view details

Ahmed Elsabbahy

commit sha 0671f1547533e2b1b5678db098048abf90e0f0cb

Changes and updates in go.mod and adding go.sum (#501) Building goss I noticed that the content of go.mod changed. Some dependencies have updates and some are siply marked as being indirect depdencies. I've also added go.sum, since I think it makes sense to add this to VCS. This lets other know that they should get a working build with this specific set of verified dependencies.

view details

pimperator

commit sha e1803030ee42480ffc0b77f6da5f270089821a04

issue-469 (#471) updateing latest-tag to 0.3.7

view details

pimperator

commit sha e8d6a96ef18f1504184f5be5b2ed48d8cd5aee9e

issue-469 (#472) introducing new variable LATEST_URL which points to latest tag on github variable LATEST is filled now dynamically with either wget or curl validating wether cut and wget or curl is present

view details

Ahmed Elsabbahy

commit sha 8700b32615ff798fe6fe8c601b87009befdde8a1

Drop cut dependency. Do not check for curl/wget since curl is needed later in the script. Remove fall-back version (#502)

view details

Christian Muehlhaeuser

commit sha c81d32662d888343ccb78be157ad2782fc1a7ac9

Gofmt all the code (#467)

view details

Christopher Fenner

commit sha 61d682ecae1937d363b74ef2762b299b522fbc18

correct format values (#466)

view details

Christopher Fenner

commit sha ed6e4cda1babc7b061544e9867cb12d5428cffca

fix typos (#463)

view details

push time in 3 months

pull request commentaelsabbahy/goss

add "kgoss" kubectl wrapper to test containers in Kubernetes

Thanks @aelsabbahy, glad to contribute! Working on removing the install commands and some minor touchups now.

joshgav

comment created time in 3 months

startedaws/aws-service-operator-k8s

started time in 4 months

push eventjoshgav/openshift-jenkins-vault-agent

Josh Gavant

commit sha 647cba7eab67ca6655b178a7cb75781afcc0c1af

fix bugs

view details

push time in 4 months

create barnchjoshgav/openshift-jenkins-vault-agent

branch : master

created branch time in 4 months

created repositoryjoshgav/openshift-jenkins-vault-agent

Adds an agent with Vault installed for use in OpenShift Jenkins pipelines.

created time in 4 months

issue commentAzure/azure-sdk-for-go

Azure Functions for Go

I'm no longer at Microsoft so unfortunately can't tell you the current state of this anymore. We'll have to wait for the current team to reply.

joshgav

comment created time in 4 months

push eventjoshgav/dotfiles

Josh Gavant

commit sha 774ca295949de25a6ddedaddda3db3b5ea6ab314

add vim-go

view details

push time in 5 months

pull request commentkubernetes/website

correct link to storage provisioner lib repo

I submitted the CLA.

joshgav

comment created time in 6 months

PR opened kubernetes/website

correct link to storage provisioner lib repo
+7 -6

0 comment

1 changed file

pr created time in 6 months

push eventjoshgav/website

Josh Gavant

commit sha ef6a449d3d6fca9ad3fc10bccbe4587979e8b0fb

correct link to storage provisioner lib repo

view details

push time in 6 months

fork joshgav/website

Kubernetes website and documentation repo:

https://kubernetes.io

fork in 6 months

more