Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

GoCD

209
325
+ 1
207
Kubernetes

60.4K
52.2K
+ 1
685
Add tool

Go.CD vs Kubernetes: What are the differences?

Developers describe Go.CD as "Open source continuous delivery tool allows for advanced workflow modeling and dependencies management". GoCD is an open source continuous delivery server created by ThoughtWorks. GoCD offers business a first-class build and deployment engine for complete control and visibility. On the other hand, Kubernetes is detailed as "Manage a cluster of Linux containers as a single system to accelerate Dev and simplify Ops". Kubernetes is an open source orchestration system for Docker containers. It handles scheduling onto nodes in a compute cluster and actively manages workloads to ensure that their state matches the users declared intentions.

Go.CD belongs to "Continuous Integration" category of the tech stack, while Kubernetes can be primarily classified under "Container Tools".

Some of the features offered by Go.CD are:

  • Model complex workflows with dependency management and parallel execution
  • Easy to pass once-built binaries between stages
  • Visibility into your end-to-end workflow. Track a change from commit to deploy at a glance

On the other hand, Kubernetes provides the following key features:

  • Lightweight, simple and accessible
  • Built for a multi-cloud world, public, private or hybrid
  • Highly modular, designed so that all of its components are easily swappable

"Open source" is the primary reason why developers consider Go.CD over the competitors, whereas "Leading docker container management solution" was stated as the key factor in picking Kubernetes.

Go.CD and Kubernetes are both open source tools. It seems that Kubernetes with 55.1K GitHub stars and 19.1K forks on GitHub has more adoption than Go.CD with 5.02K GitHub stars and 791 GitHub forks.

Google, Slack, and Shopify are some of the popular companies that use Kubernetes, whereas Go.CD is used by Auto Trader, ThoughtWorks, and Hazeorid. Kubernetes has a broader approval, being mentioned in 1046 company stacks & 1096 developers stacks; compared to Go.CD, which is listed in 28 company stacks and 8 developer stacks.

Advice on GoCD and Kubernetes
Mohammad Hossein Amri
Chief Technology Officer at Planally · | 3 upvotes · 534.3K views
Needs advice
on
GoCDGoCD
and
JenkinsJenkins

I'm open to anything. just want something that break less and doesn't need me to pay for it, and can be hosted on Docker. our scripting language is powershell core. so it's better to support it. also we are building dotnet core in our pipeline, so if they have anything related that helps with the CI would be nice.

See more
Replies (1)
Ankit Malik
Software Developer at CloudCover · | 1 upvotes · 517K views
Recommends
on
Google Cloud BuildGoogle Cloud Build

Google cloud build can help you. It is hosted on cloud and also provide reasonable free quota.

See more
Decisions about GoCD and Kubernetes
Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH · | 30 upvotes · 12.2M views

Our whole DevOps stack consists of the following tools:

  • GitHub (incl. GitHub Pages/Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
  • Respectively Git as revision control system
  • SourceTree as Git GUI
  • Visual Studio Code as IDE
  • CircleCI for continuous integration (automatize development process)
  • Prettier / TSLint / ESLint as code linter
  • SonarQube as quality gate
  • Docker as container management (incl. Docker Compose for multi-container application management)
  • VirtualBox for operating system simulation tests
  • Kubernetes as cluster management for docker containers
  • Heroku for deploying in test environments
  • nginx as web server (preferably used as facade server in production environment)
  • SSLMate (using OpenSSL) for certificate management
  • Amazon EC2 (incl. Amazon S3) for deploying in stage (production-like) and production environments
  • PostgreSQL as preferred database system
  • Redis as preferred in-memory database/store (great for caching)

The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:

  • Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
  • Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
  • Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
  • Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
  • Scalability: All-in-one framework for distributed systems.
  • Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.
See more
Manage your open source components, licenses, and vulnerabilities
Learn More
Pros of GoCD
Pros of Kubernetes
  • 32
    Open source
  • 27
    Pipeline dependencies
  • 25
    Pipeline structures
  • 22
    Can run jobs in parallel
  • 20
    Very flexible
  • 15
    Plugin architecture
  • 13
    Environments can keep config secure
  • 12
    Great UI
  • 10
    Good user roles and permissions
  • 9
    Supports many material dependencies
  • 7
    Fan-in, Fan-out
  • 6
    Designed for cd not just ci
  • 4
    Empowers product people to make delivery decisions
  • 2
    Flexible & easy deployment
  • 2
    Pass around artifacts
  • 1
    Build once
  • 166
    Leading docker container management solution
  • 130
    Simple and powerful
  • 108
    Open source
  • 76
    Backed by google
  • 58
    The right abstractions
  • 26
    Scale services
  • 20
    Replication controller
  • 11
    Permission managment
  • 9
    Supports autoscaling
  • 8
    Cheap
  • 8
    Simple
  • 7
    Self-healing
  • 5
    Open, powerful, stable
  • 5
    Promotes modern/good infrascture practice
  • 5
    Reliable
  • 5
    No cloud platform lock-in
  • 4
    Scalable
  • 4
    Quick cloud setup
  • 3
    Cloud Agnostic
  • 3
    Custom and extensibility
  • 3
    A self healing environment with rich metadata
  • 3
    Captain of Container Ship
  • 3
    Backed by Red Hat
  • 3
    Runs on azure
  • 2
    Expandable
  • 2
    Sfg
  • 2
    Everything of CaaS
  • 2
    Gke
  • 2
    Golang
  • 2
    Easy setup

Sign up to add or upvote prosMake informed product decisions

Cons of GoCD
Cons of Kubernetes
  • 2
    Lack of plugins
  • 2
    Horrible ui
  • 1
    No support
  • 16
    Steep learning curve
  • 15
    Poor workflow for development
  • 8
    Orchestrates only infrastructure
  • 4
    High resource requirements for on-prem clusters
  • 2
    Too heavy for simple systems
  • 1
    Additional vendor lock-in (Docker)
  • 1
    More moving parts to secure
  • 1
    Additional Technology Overhead

Sign up to add or upvote consMake informed product decisions

98
198
824
3.9K
58.3K
- No public GitHub repository available -

What is GoCD?

GoCD is an open source continuous delivery server created by ThoughtWorks. GoCD offers business a first-class build and deployment engine for complete control and visibility.

What is Kubernetes?

Kubernetes is an open source orchestration system for Docker containers. It handles scheduling onto nodes in a compute cluster and actively manages workloads to ensure that their state matches the users declared intentions.

Need advice about which tool to choose?Ask the StackShare community!

What companies use GoCD?
What companies use Kubernetes?
Manage your open source components, licenses, and vulnerabilities
Learn More

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with GoCD?
What tools integrate with Kubernetes?

Sign up to get full access to all the tool integrationsMake informed product decisions

Blog Posts

Kubernetesetcd+2
2
1219
Dec 8 2020 at 5:50PM

DigitalOcean

GitHubMySQLPostgreSQL+11
2
2497
PythonDockerKubernetes+7
3
1192
May 21 2020 at 12:02AM

Rancher Labs

KubernetesAmazon EC2Grafana+12
5
1569
Apr 16 2020 at 5:34AM

Rancher Labs

KubernetesRancher+2
2
1001
What are some alternatives to GoCD and Kubernetes?
Jenkins
In a nutshell Jenkins CI is the leading open-source continuous integration server. Built with Java, it provides over 300 plugins to support building and testing virtually any project.
GitLab CI
GitLab offers a continuous integration service. If you add a .gitlab-ci.yml file to the root directory of your repository, and configure your GitLab project to use a Runner, then each merge request or push triggers your CI pipeline.
Bamboo
Focus on coding and count on Bamboo as your CI and build server! Create multi-stage build plans, set up triggers to start builds upon commits, and assign agents to your critical builds and deployments.
TeamCity
TeamCity is a user-friendly continuous integration (CI) server for professional developers, build engineers, and DevOps. It is trivial to setup and absolutely free for small teams and open source projects.
Concourse
Concourse's principles reduce the risk of switching to and from Concourse, by encouraging practices that decouple your project from your CI's little details, and keeping all configuration in declarative files that can be checked into version control.
See all alternatives