profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/liamawhite/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.
Liam White liamawhite @tetrateio Seattle, WA USA www.linkedin.com/in/liam-white Software Engineer @tetrateio. @istio Maintainer.

liamawhite/istio-dev-framework 2

Live debug Istio code in a Kubernetes cluster.

liamawhite/amalgam8 0

Content and Version-based Routing Fabric for Polyglot Microservices

liamawhite/api 0

API, config and standard vocabulary definitions for the Istio project

liamawhite/cgm-remote-monitor 0

nightscout web monitor

liamawhite/chartmuseum 0

Helm Chart Repository with support for Amazon S3 and Google Cloud Storage

liamawhite/community 0

Istio governance material.

liamawhite/docker.github.io 0

Source repo for Docker's Documentation

issue commentistio/istio

Multi-Istio deployments in same k8s cluster

I think you would also need to filter out Istio CRs to avoid cross-contamination. i.e. If I create a service entry with exportTo: ['*'] in a namespace not managed by a given mesh, it shouldn't appear in Envoys for that mesh. Having spoken to @harveyxia, #29802 doesn't ignore Istio resources created in a given namespace.

l8huang

comment created time in 25 days

issue commentpulumi/pulumi

Provider gRPC client logging causes failures.

I did some more investigating and after deleting my go mod cache and re-downloading everything it appears to not be an issue. I have no idea what was causing it.

liamawhite

comment created time in 2 months

issue closedpulumi/pulumi

Provider gRPC client logging causes failures.

I'm trying to write my own provider using the boilerplate template but I think there is a breaking bug. From what I can tell the provider is expected to output to stdout the port it is listening on, but what appears to happen is that grpc logging beats it to it.

When I run Pulumi up I get:

pulumi:providers:tsb (tsb):
    error: tsb (resource) plugin [/Users/liamwhite/go/bin/pulumi-resource-tsb] wrote a non-numeric port to stdout ('2021-05-27T13:44:04.073942Z	info	[core]parsed scheme: ""'): strconv.Atoi: parsing "2021-05-27T13:44:04.073942Z\tinfo\t[core]parsed scheme: \"\"": invalid syntax

I can fix this by manually configuring the grpc logger to either info log to stderr (or discard).

// NewHostClient dials the target address, connects over gRPC, and returns a client interface.
func NewHostClient(addr string) (*HostClient, error) {
	grpclog.SetLoggerV2(grpclog.NewLoggerV2(os.Stderr, os.Stderr, os.Stderr)) // <-----------
	conn, err := grpc.Dial(
		addr,
		grpc.WithInsecure(),
		grpc.WithUnaryInterceptor(rpcutil.OpenTracingClientInterceptor()),
		rpcutil.GrpcChannelOptions(),
	)
...

The only problem with sending to stderr is that it shows up in diagnostics so it may be preferable to io.Discard instead.

closed time in 2 months

liamawhite

issue commentpulumi/pulumi

Provider gRPC client logging causes failures.

@lukehoban I wasn't logging anything this just happened importing the standard boilerplate Main function @3.3.1.

liamawhite

comment created time in 2 months

issue openedpulumi/pulumi

Provider gRPC client logging causes failures.

I'm trying to write my own provider using the boilerplate template but I think there is a breaking bug. From what I can tell the provider is expected to output to stdout the port it is listening on, but what appears to happen is that grpc logging beats it to it.

When I run Pulumi up I get:

pulumi:providers:tsb (tsb):
    error: tsb (resource) plugin [/Users/liamwhite/go/bin/pulumi-resource-tsb] wrote a non-numeric port to stdout ('2021-05-27T13:44:04.073942Z	info	[core]parsed scheme: ""'): strconv.Atoi: parsing "2021-05-27T13:44:04.073942Z\tinfo\t[core]parsed scheme: \"\"": invalid syntax

I can fix this by manually configuring the grpc logger to either info log to stderr (or discard).

// NewHostClient dials the target address, connects over gRPC, and returns a client interface.
func NewHostClient(addr string) (*HostClient, error) {
	grpclog.SetLoggerV2(grpclog.NewLoggerV2(os.Stderr, os.Stderr, os.Stderr))
	conn, err := grpc.Dial(
		addr,
		grpc.WithInsecure(),
		grpc.WithUnaryInterceptor(rpcutil.OpenTracingClientInterceptor()),
		rpcutil.GrpcChannelOptions(),
	)
...

The only problem with sending to stderr is that it shows up in diagnostics so it may be preferable to io.Discard instead.

created time in 2 months

PR opened pulumi/pulumi

Populate package.json version to match provider version

As the version is hardcoded, whenever I rebuild I get:

Diagnostics:
  pulumi:providers:tsb (tsb):
    error: pulumi:providers:tsb resource 'tsb's property 'version' value {${VERSION}} has a problem: could not parse provider version: Invalid character(s) found in major number "${VERSION}"

Is there any reason we can't just populate this with the provider version?

+1 -1

0 comment

1 changed file

pr created time in 2 months

push eventliamawhite/pulumi

Liam White

commit sha 79d11ba433c8bc9f91b3e9ca3d9ddb32d19acd68

Populate package.json version to match provider version As version is hardcoded, when I rebuild I get: ``` Diagnostics: pulumi:providers:tsb (tsb): error: pulumi:providers:tsb resource 'tsb's property 'version' value {${VERSION}} has a problem: could not parse provider version: Invalid character(s) found in major number "${VERSION}" ``` Is there any reason we can't just populate this with the provider version?

view details

push time in 2 months

fork liamawhite/pulumi

Pulumi - Modern Infrastructure as Code. Any cloud, any language 🚀

https://www.pulumi.com

fork in 2 months

PullRequestReviewEvent

push eventliamawhite/kindle-parser

Liam White

commit sha d4aaf68dcb246580eb606015deeb8549b4a6a411

initial functionality Signed-off-by: Liam White <liam@tetrate.io>

view details

push time in 2 months

delete branch liamawhite/kindle-parser

delete branch : master

delete time in 2 months

create barnchliamawhite/kindle-parser

branch : master

created branch time in 2 months

create barnchliamawhite/kindle-parser

branch : main

created branch time in 2 months

created repositoryliamawhite/kindle-parser

Prints Kindle exports into a Roam Research friendly output.

created time in 2 months

PullRequestReviewEvent

issue commentjetstack/cert-manager

Can't create issuer when running in aws eks fargate

Hi all,

I raised a support ticket with AWS and this was the response I got. I haven't got time to verify this works but let me know if it does!


From their investigation, the issue mentioned is more related to cert-manager setup. The cert-manager-webhook deployment uses port 10250 which is also used for kubelet on the Fargate pods. Therefore when the connection was made to the cert-manager-webhook service it was reporting the error with ip address corresponding to pod cert-manager-webhook.

Here are the steps to address the error:

•Updated the deployment and changed port references from 10250 to 10260 at --secure-port and containerPort.

  kubectl edit deployment -n cert-manager cert-manager-webhook

•Updated the service and changed port reference from 10250 to 10260 at targetPort.

  kubectl edit svc -n cert-manager cert-manager-webhook

•Wait for the new pod to appear for the updated deployment. •Create an issuer now with same command: cat <<EOF | kubectl apply -f - apiVersion: cert-manager.io/v1alpha2 kind: Issuer metadata: name: selfsigned-issuer namespace: appspace spec: selfSigned: {} EOF issuer.cert-manager.io/selfsigned-issuer created

kesse

comment created time in 3 months