Let’s go on a trip through history
@jbaruch
|
jfrog.com/shownotes
|
gocenter.io

A quick history of go
Go 1.8
Introduction of Go plugins
Go 1.0
Go 1.10
First major milestone as a long term stable release
Changes to the toolchain, runtime, and libs Go 1.5
First release to no longer use C (except for cgo) Support for Vendoring
2012
2015
@jbaruch
2017
|
jfrog.com/shownotes
|
gocenter.io
2018

“Tis impossible to be sure of anything but Death and Taxes” - Christopher Bullock
@jbaruch
|
jfrog.com/shownotes
|
gocenter.io

A quick history of go
Go 1.8
Introduction of Go plugins
Go 1.0
Go 1.10
First major milestone as a long term stable release
Changes to the toolchain, runtime, and libs Go 1.5
Go 1.11
First release to no longer use C (except for cgo)
Go Modules!
Support for Vendoring
2012
2015
2017
@jbaruch
|
jfrog.com/shownotes
2018
|
gocenter.io
2018

So, what are modules?
Official Dependency Management
No more GOPATH
@jbaruch
|
jfrog.com/shownotes
|
In one single tool
gocenter.io

Forking is not always good, bad forking is always bad
And that’s what vendoring is
@jbaruch
|
jfrog.com/shownotes
|
gocenter.io

In software Immutable and repeatable are really important Immutable dependencies The best way to guarantee issues is force push
Lost Dependencies Who doesn’t remember left-pad with Node.js?
Trust Do you trust your colleagues? What about the rest of the Internet?
@jbaruch
|
jfrog.com/shownotes
|
gocenter.io

Deployments using helm • Helm Charts are versioned • Separate value files per environment • Having one of the cofounders of Helm at our company also doesn’t hurt
@jbaruch
|
jfrog.com/shownotes
|
gocenter.io
Config

Scaling on many levels
Node
Compute
Provision nodes when needed
Run more microservices
Messaging
Up and Down
Scaling based on queue depth
What goes up must come down… usually
@jbaruch
|
jfrog.com/shownotes
|
gocenter.io
Concurrency

#5
Dare to dream
@jbaruch
|
jfrog.com/shownotes
|
gocenter.io

What’s next for gocenter ChatOps
Use Slack to let teams take more control
In-Cluster Artifactory
Making upgrades more seamless, but…
Your Feedback
We want to hear from you what we need to improve!
@jbaruch
|
jfrog.com/shownotes
|
gocenter.io

Link for this presentation:

HTML code for embedding:

Share on social media:

Today, Kubernetes is the defacto standard if you want to run container workloads in a production environment. As we set out to build our next generation of products, and run them smoothly in the cloud, we needed to move to Kubernetes too! In the process of building tools like KubeXray and GoCenter we learned a whole bunch.

Join this talk to learn how to get started with Kubernetes and how we got started at JFrog building our new tools. After the session you will know:
– How we got to Kubernetes (and why we chose it)
– How to know what you have in your apps and containers (and how we built ours)
– How we’re running GoCenter at scale.