profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/eddiezane/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.
Eddie Zaneski eddiezane @AWS Denver, CO Dev Advocate @aws. Love me some @kubernetes, Go, and JavaScript.

eddiezane/dotfiles 18

doot doot

eddiezane/es6-jspm-react-example 10

Quick demo using Giphy

eddiezane/contribot 4

Reward open source contributors with swag!

eddiezane/Burrito-Decider 3

Because who doesn't like burritos?

aliciahurst/pizzafy 1

The beginning of developing Pizzafy, switched to another, private repo for the rest, though

DrewBradley/dnd-monstronomicon 1

Dungeon Masters building encounters in Dungeons & Dragons 5th edition can search and filter monsters, and add them to an encounter.

eddiezane/Biographer 1

HackRU Spring 2013

eddiezane/dodyndns 1

Updates a DigitalOcean domain record with your public IP

eddiezane/Electron-Twilio-IPM 1

https://www.twilio.com/blog/2015/12/getting-started-with-electron-building-a-desktop-chat-app.html

eddiezane/Foto-Friendzy 1

TechGirlz Summer Camp 2014

release facebook/docusaurus

v2.0.0-beta.2

released time in an hour

release lostisland/faraday

v1.4.3

released time in 4 hours

release mjmlio/mjml

v4.10.1

released time in 4 hours

issue commentkubernetes/kubectl

Autocomplete for container name in kubectl exec

@fejta-bot: Closing this issue.

<details>

In response to this:

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community. /close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. </details>

thomas-riccardi

comment created time in 6 hours

issue closedkubernetes/kubectl

Autocomplete for container name in kubectl exec

<!-- Please only use this template for submitting enhancement requests -->

What would you like to be added: Auto-completion for container name in kubectl exec. kubectl exec -it mypod -c [TAB]

Currently it proposes pod names after -c (in fact after anything ~unknown it seems).

More generally, it should stop proposing pod names after the first pod name in cmdline, especially after --.

(tested with kubectl v1.18.3)

Why is this needed: Autocompletion allow smooth workload exploration and usage: no need to explicitly discover with kubectl describe pod mypod then copy/paste the container name in kubectl exec cmdline.

(container name autocompletion already works great for kubectl logs mypod)

closed time in 6 hours

thomas-riccardi

issue commentkubernetes/kubectl

Autocomplete for container name in kubectl exec

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community. /close

thomas-riccardi

comment created time in 6 hours

startededdiezane/sendgrid-actionmailer

started time in 10 hours

release sass/node-sass

v6.0.1

released time in 10 hours

release mui-org/material-ui

v5.0.0-alpha.38

released time in 15 hours

release vercel/next.js

v11.0.2-canary.0

released time in 18 hours

release vercel/pkg

5.3.0

released time in 18 hours

startededdiezane/lunchy

started time in 21 hours

PR closed kubernetes/kubectl

Added community note to bug report and enhancement issue templates area/kubectl cncf-cla: yes sig/cli sig/contributor-experience size/XS
+9 -0

4 comments

2 changed files

brianpursley

pr closed time in a day

pull request commentkubernetes/kubectl

Added community note to bug report and enhancement issue templates

I don't know why I opened this against the kubectl repo and not kubernetes/staging :laughing:

For some reason I thought the .github directory was only in this repo and not in staging. I'll close this and reopen in the main repo

brianpursley

comment created time in a day

issue commentkubernetes/kubectl

Can't read certificate authority from named pipe

https://github.com/kubernetes/kubernetes/pull/97855 , related issue

aeriksson

comment created time in a day

issue commentkubernetes/kubectl

Can't read certificate authority from named pipe

Every time we set up a DiscoveryClient, we will have to set up a new REST client, therefore we will have to set up the TLS connection again, that's why it's showing errors given the fact that /dev/fd/63 can only be read once

aeriksson

comment created time in 2 days

issue commentkubernetes/kubectl

`kubectl run` does not fail when you do not pass a NAME, when you pass a --command

@fejta-bot: Closing this issue.

<details>

In response to this:

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community. /close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. </details>

sallyom

comment created time in 2 days

issue closedkubernetes/kubectl

`kubectl run` does not fail when you do not pass a NAME, when you pass a --command

What happened:

$ kubectl run --image fedora --command -- sleep 100
pod/sleep created

the pod is created, then crashloops with

container create failed: time="2020-10-02T16:28:22Z" level=error msg="container_linux.go:366: starting container process caused: exec: \"100\": executable file not found in $PATH"

this should instead error w/ the msg,

error: NAME is required for run
See 'kubectl run -h' for help and examples

How to reproduce it (as minimally and precisely as possible): $ kubectl run --image fedora --command -- sleep 100 the pod/sleep is created, and if you kubectl get pod/sleep -o yaml you'll see the error noted above.

Environment: latest master build

closed time in 2 days

sallyom

issue commentkubernetes/kubectl

`kubectl run` does not fail when you do not pass a NAME, when you pass a --command

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community. /close

sallyom

comment created time in 2 days

issue commentkubernetes/kubectl

Can't read certificate authority from named pipe

@eddiezane , did some diggings

aeriksson

comment created time in 2 days

created tagkubernetes/kubectl

tagv0.22.0-beta.0

Issue tracker and mirror of kubectl code

created time in 2 days

created tagkubernetes/kubectl

tagkubernetes-1.22.0-beta.0

Issue tracker and mirror of kubectl code

created time in 2 days

release vercel/next.js

v11.0.1

released time in 2 days

release vercel/next.js

v11.0.1-canary.8

released time in 2 days

release vercel/next.js

v11.0.1-canary.7

released time in 2 days

issue commentkubernetes/kubectl

Add ANSI colors to kubectl describe and other outputs

or

kubectl … | yq e -P
izelnakri

comment created time in 2 days

issue commentkubernetes/kubectl

[Windows] kubectl run not accepting valid JSON as --override on Windows (same JSON works on Mac)

The solution suggested by @woodwardmatt works for me, however, I don't understand why converting a string of JSON to JSON is the solution here. 🤔

psreed

comment created time in 2 days

issue commentkubernetes/kubectl

Add ANSI colors to kubectl describe and other outputs

If you're using the fish shell and bat, you can define a function like:

function kat
  command kubectl $argv -o yaml | bat -l yaml
end

You could also use yh mentioned above instead of bat, of course.

izelnakri

comment created time in 2 days

release grpc-ecosystem/grpc-gateway

v2.5.0

released time in 3 days

issue commentkubernetes/kubectl

'kubectl exec --tty --stdin' "leaking" proccess inside pod when terminated

@xelxebar: This issue is currently awaiting triage.

SIG CLI takes a lead on issue triage for this repo, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

<details>

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. </details>

xelxebar

comment created time in 3 days