mirror of
https://github.com/kemko/nomad.git
synced 2026-01-01 16:05:42 +03:00
website: Update k8s comparison docs, ecosystem and community (#9557)
* website: add k8s vs callout to homepage * website: move resources to community * website: add k8s comparison, ecosytem to docs * website: update redirects * website: fix homepage link * website: fix sidebar data * Update website/pages/docs/nomad-vs-kubernetes/index.mdx Co-authored-by: changli0617 <39781496+changli0617@users.noreply.github.com> * Update website/pages/docs/nomad-vs-kubernetes/alternative.mdx Co-authored-by: changli0617 <39781496+changli0617@users.noreply.github.com> * Update website/pages/docs/nomad-vs-kubernetes/alternative.mdx Co-authored-by: changli0617 <39781496+changli0617@users.noreply.github.com> * Update website/pages/docs/nomad-vs-kubernetes/alternative.mdx Co-authored-by: changli0617 <39781496+changli0617@users.noreply.github.com> Co-authored-by: changli0617 <39781496+changli0617@users.noreply.github.com>
This commit is contained in:
Mike Wickett
@@ -1,7 +1,11 @@
|
||||
export default function FeaturesList({ title, items }) {
|
||||
export default function FeaturesList({ title, items, intro }) {
|
||||
return (
|
||||
<div className="g-features-list g-grid-container">
|
||||
<h2 className="g-type-display-2">{title}</h2>
|
||||
<div
|
||||
className="intro-container"
|
||||
dangerouslySetInnerHTML={{ __html: intro }}
|
||||
/>
|
||||
<div className="items-container">
|
||||
{items.map(({ title, content, icon }) => (
|
||||
<div key={title} className="item">
|
||||
|
||||
@@ -4,7 +4,18 @@
|
||||
& h2 {
|
||||
text-align: center;
|
||||
margin-top: 0;
|
||||
margin-bottom: 32px;
|
||||
}
|
||||
|
||||
& .intro-container {
|
||||
text-align: center;
|
||||
max-width: 600px;
|
||||
margin: 0 auto;
|
||||
margin-bottom: 64px;
|
||||
|
||||
& a {
|
||||
color: var(--nomad);
|
||||
}
|
||||
}
|
||||
|
||||
& .items-container {
|
||||
|
||||
@@ -29,7 +29,7 @@ export default [
|
||||
'windows-service',
|
||||
],
|
||||
},
|
||||
{category: 'upgrade', content: ['upgrade-specific']},
|
||||
{ category: 'upgrade', content: ['upgrade-specific'] },
|
||||
{
|
||||
category: 'integrations',
|
||||
content: ['consul-integration', 'consul-connect', 'vault-integration'],
|
||||
@@ -50,7 +50,7 @@ export default [
|
||||
'consensus',
|
||||
'filesystem',
|
||||
'gossip',
|
||||
'security'
|
||||
'security',
|
||||
],
|
||||
},
|
||||
{
|
||||
@@ -159,17 +159,20 @@ export default [
|
||||
'snapshot-save',
|
||||
],
|
||||
},
|
||||
{category: 'plugin', content: ['status']},
|
||||
{ category: 'plugin', content: ['status'] },
|
||||
{
|
||||
category: 'quota',
|
||||
content: ['apply', 'delete', 'init', 'inspect', 'list', 'status'],
|
||||
},
|
||||
{category: 'recommendation', content: ['apply', 'dismiss', 'info', 'list']},
|
||||
{category: 'scaling', content: ['policy-info', 'policy-list']},
|
||||
{category: 'sentinel', content: ['apply', 'delete', 'list', 'read']},
|
||||
{category: 'server', content: ['force-leave', 'join', 'members']},
|
||||
{
|
||||
category: 'recommendation',
|
||||
content: ['apply', 'dismiss', 'info', 'list'],
|
||||
},
|
||||
{ category: 'scaling', content: ['policy-info', 'policy-list'] },
|
||||
{ category: 'sentinel', content: ['apply', 'delete', 'list', 'read'] },
|
||||
{ category: 'server', content: ['force-leave', 'join', 'members'] },
|
||||
'status',
|
||||
{category: 'system', content: ['gc', 'reconcile-summaries']},
|
||||
{ category: 'system', content: ['gc', 'reconcile-summaries'] },
|
||||
'ui',
|
||||
'version',
|
||||
{
|
||||
@@ -270,7 +273,12 @@ export default [
|
||||
{
|
||||
category: 'ipnet',
|
||||
name: 'IP Network Functions',
|
||||
content: ['cidrhost', 'cidrnetmask', 'cidrsubnet', 'cidrsubnets'],
|
||||
content: [
|
||||
'cidrhost',
|
||||
'cidrnetmask',
|
||||
'cidrsubnet',
|
||||
'cidrsubnets',
|
||||
],
|
||||
},
|
||||
{
|
||||
category: 'numeric',
|
||||
@@ -392,7 +400,7 @@ export default [
|
||||
content: ['nvidia', 'community'],
|
||||
},
|
||||
'schedulers',
|
||||
{category: 'runtime', content: ['environment', 'interpolation']},
|
||||
{ category: 'runtime', content: ['environment', 'interpolation'] },
|
||||
{
|
||||
category: 'autoscaling',
|
||||
content: [
|
||||
@@ -419,19 +427,26 @@ export default [
|
||||
'metrics',
|
||||
{
|
||||
title: 'Cluster Management',
|
||||
href: 'https://learn.hashicorp.com/collections/nomad/manage-clusters'
|
||||
href: 'https://learn.hashicorp.com/collections/nomad/manage-clusters',
|
||||
},
|
||||
{
|
||||
title: 'Transport Security',
|
||||
href: 'https://learn.hashicorp.com/collections/nomad/transport-security'
|
||||
href:
|
||||
'https://learn.hashicorp.com/collections/nomad/transport-security',
|
||||
},
|
||||
{
|
||||
title: 'Access Control',
|
||||
href: 'https://learn.hashicorp.com/collections/nomad/access-control'
|
||||
}
|
||||
]
|
||||
href: 'https://learn.hashicorp.com/collections/nomad/access-control',
|
||||
},
|
||||
],
|
||||
},
|
||||
'------------',
|
||||
{
|
||||
category: 'nomad-vs-kubernetes',
|
||||
content: ['alternative', 'supplement'],
|
||||
},
|
||||
'ecosystem',
|
||||
'who-uses-nomad',
|
||||
'enterprise',
|
||||
'faq',
|
||||
]
|
||||
|
||||
@@ -7,8 +7,7 @@
|
||||
|
||||
export default [
|
||||
'use-cases',
|
||||
'who-uses-nomad',
|
||||
{ category: 'vs', content: ['kubernetes', 'ecs', 'mesos', 'terraform'] },
|
||||
{ category: 'vs', content: ['ecs', 'mesos', 'terraform'] },
|
||||
{
|
||||
category: 'getting-started',
|
||||
content: ['running', 'jobs', 'cluster', 'ui', 'next-steps'],
|
||||
|
||||
@@ -39,8 +39,8 @@ export default [
|
||||
type: 'inbound',
|
||||
},
|
||||
{
|
||||
text: 'Resources',
|
||||
url: '/resources',
|
||||
text: 'Community',
|
||||
url: '/community',
|
||||
type: 'inbound',
|
||||
},
|
||||
]
|
||||
|
||||
135
website/pages/community/index.jsx
Normal file
135
website/pages/community/index.jsx
Normal file
@@ -0,0 +1,135 @@
|
||||
import Head from 'next/head'
|
||||
import HashiHead from '@hashicorp/react-head'
|
||||
import Content from '@hashicorp/react-content'
|
||||
|
||||
export default function ResourcesPage() {
|
||||
return (
|
||||
<>
|
||||
<HashiHead
|
||||
is={Head}
|
||||
title="Community | Nomad by HashiCorp"
|
||||
description="Nomad is widely deployed across a range of enterprises and business verticals."
|
||||
/>
|
||||
<div id="p-resources" className="g-grid-container">
|
||||
<Content
|
||||
product="nomad"
|
||||
content={
|
||||
<>
|
||||
<h2>Community</h2>
|
||||
<p>
|
||||
Nomad is widely adopted and used in production by organizations
|
||||
like Cloudflare, Roblox, Pandora, PagerDuty, and more.
|
||||
</p>
|
||||
<p>
|
||||
This is a collection of resources for joining our community and
|
||||
learning Nomad's real world use-cases.
|
||||
</p>
|
||||
<p>
|
||||
<strong>Discussion Forum</strong>
|
||||
<ul>
|
||||
<li>
|
||||
<a href="https://discuss.hashicorp.com/c/nomad">
|
||||
HashiCorp Discuss
|
||||
</a>
|
||||
</li>
|
||||
</ul>
|
||||
</p>
|
||||
<p>
|
||||
<strong>Virtual Talks</strong>
|
||||
<ul>
|
||||
<li>
|
||||
<a href="https://www.hashicorp.com/resources/nomad-scheduling-101-why-let-container-runtimes-have-all-the-fun/">
|
||||
6/9 Scheduling Containers, .NET, Java Applications with
|
||||
Nomad (2020)
|
||||
</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href="https://www.hashicorp.com/resources/nomad-ci-cd-developer-workflows-and-integrations/">
|
||||
5/29 Build a CI/CD Pipeline with Nomad & Gitlab (2020)
|
||||
</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href="https://www.hashicorp.com/resources/cloud-bursting-made-real-with-nomad-and-consul/">
|
||||
5/29 Cloud Bursting Demo with Nomad & Consul (2020)
|
||||
</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href="https://www.hashicorp.com/resources/nomad-expert-panel-live-q2-2020/">
|
||||
5/29 Nomad Expert Panel Live Q&A (2020)
|
||||
</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href="https://www.hashicorp.com/resources/governance-for-multiple-teams-sharing-a-nomad-cluster/">
|
||||
5/15 Governance for Multiple Teams Sharing a Nomad Cluster
|
||||
(2020)
|
||||
</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href="https://www.hashicorp.com/resources/modern-scheduling-for-modern-applications-with-nomad/">
|
||||
{' '}
|
||||
4/20 Modern Scheduling for Modern Applications with Nomad
|
||||
(2020)
|
||||
</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href="https://www.hashicorp.com/resources/solutions-engineering-hangout-integrating-nomad-with-vault/">
|
||||
{' '}
|
||||
4/17 Integrating Nomad with Vault Demo (2020)
|
||||
</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href="https://www.hashicorp.com/resources/nomad-tech-deep-dive-autoscaling-csi-plugins-and-more/">
|
||||
4/14 Nomad Deep Dive: Autoscaling, CSI Plugins, and More
|
||||
(2020)
|
||||
</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href="https://www.hashicorp.com/resources/nomad-virtual-day-2020-panel-discussion/">
|
||||
3/16 Nomad Panel Discussion with Roblox (2020)
|
||||
</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href="https://www.hashicorp.com/resources/hashicorp-nomad-vs-kubernetes-comparing-complexity/">
|
||||
3/3 Nomad vs. Kubernetes - Comparing Complexity (2020)
|
||||
</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href="https://www.hashicorp.com/resources/ground-control-to-nomad-job-dispatch/">
|
||||
2/27 Ground Control to Nomad Job Dispatch (2020)
|
||||
</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href="https://www.hashicorp.com/resources/nomad-best-practices-for-reliable-deploys/">
|
||||
2/27 Best Practices for Reliable Deploys on Nomad (2020)
|
||||
</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href="https://www.hashicorp.com/resources/monitoring-nomad-with-prometheus-and-icinga/">
|
||||
2/27 Monitoring Nomad with Prometheus and Incinga (2020)
|
||||
</a>
|
||||
</li>
|
||||
</ul>
|
||||
</p>
|
||||
<p>
|
||||
<strong>Bug Tracker</strong>
|
||||
<ul>
|
||||
<li>
|
||||
<a href="https://github.com/hashicorp/nomad/issues">
|
||||
GitHub Issues
|
||||
</a>
|
||||
</li>
|
||||
</ul>
|
||||
Please only use this to report bugs. For general help, please
|
||||
use our{' '}
|
||||
<a href="https://discuss.hashicorp.com/c/nomad">
|
||||
discussion forum
|
||||
</a>
|
||||
.
|
||||
</p>
|
||||
</>
|
||||
}
|
||||
/>
|
||||
</div>
|
||||
</>
|
||||
)
|
||||
}
|
||||
200
website/pages/docs/ecosystem.mdx
Normal file
200
website/pages/docs/ecosystem.mdx
Normal file
@@ -0,0 +1,200 @@
|
||||
---
|
||||
layout: docs
|
||||
page_title: Nomad Ecosystem
|
||||
sidebar_title: Nomad Ecosystem
|
||||
description: Comparison between Nomad and Kubernetes
|
||||
---
|
||||
|
||||
# Nomad Ecosystem
|
||||
|
||||
### Continuous Integration & Delivery
|
||||
|
||||
#### GitLab
|
||||
|
||||
https://www.hashicorp.com/resources/nomad-ci-cd-developer-workflows-and-integrations
|
||||
|
||||
#### Codefresh
|
||||
|
||||
https://codefresh.io/docs/docs/yaml-examples/examples/nomad/
|
||||
|
||||
#### CircleCI
|
||||
|
||||
https://circleci.com/docs/2.0/nomad/
|
||||
|
||||
#### Drone
|
||||
|
||||
https://docs.drone.io/runner/nomad/overview/
|
||||
|
||||
#### Jenkins
|
||||
|
||||
https://plugins.jenkins.io/nomad/
|
||||
|
||||
#### Buildkite
|
||||
|
||||
https://buildkite.com/works-with/hashicorp
|
||||
|
||||
### Container Runtime
|
||||
|
||||
#### Containerd
|
||||
|
||||
https://www.nomadproject.io/docs/drivers/external/containerd
|
||||
|
||||
#### Windows IIS
|
||||
|
||||
https://github.com/Roblox/nomad-driver-iis
|
||||
|
||||
#### Jailtask
|
||||
|
||||
https://www.nomadproject.io/docs/drivers/external/jail-task-driver
|
||||
|
||||
#### Pot
|
||||
|
||||
https://github.com/trivago/nomad-pot-driver
|
||||
|
||||
#### Singularity
|
||||
|
||||
https://www.nomadproject.io/docs/drivers/external/singularity
|
||||
|
||||
#### Firecracker
|
||||
|
||||
https://www.nomadproject.io/docs/drivers/external/firecracker-task-driver
|
||||
|
||||
#### Podman
|
||||
|
||||
https://www.nomadproject.io/docs/drivers/podman
|
||||
|
||||
#### LXC
|
||||
|
||||
https://www.nomadproject.io/docs/drivers/external/lxc
|
||||
|
||||
### Application Definition & Image Build
|
||||
|
||||
#### Levant
|
||||
|
||||
https://github.com/hashicorp/levant
|
||||
|
||||
#### Packer
|
||||
|
||||
https://www.packer.io/
|
||||
|
||||
#### Waypoint
|
||||
|
||||
https://learn.hashicorp.com/collections/waypoint/get-started-nomad
|
||||
|
||||
### Container Registry
|
||||
|
||||
#### JFrog Artifactory
|
||||
|
||||
https://jfrog.com/blog/cluster-management-made-simple-with-jfrog-artifactory-and-hashicorp-nomad/
|
||||
|
||||
### Observability and Analysis
|
||||
|
||||
#### Prometheus
|
||||
|
||||
https://learn.hashicorp.com/tutorials/nomad/prometheus-metrics
|
||||
|
||||
https://learn.hashicorp.com/tutorials/nomad/dynamic-application-sizing?in=nomad/nomad-1-0#start-prometheus
|
||||
|
||||
#### Grafana
|
||||
|
||||
https://www.metricfire.com/blog/monitoring-hashicorp-nomad-with-prometheus-and-grafana/
|
||||
|
||||
#### DataDog
|
||||
|
||||
https://docs.datadoghq.com/integrations/nomad/
|
||||
|
||||
#### Turbonomics
|
||||
|
||||
https://www.youtube.com/watch?v=lwtIaPpdDsc
|
||||
|
||||
#### Circonus
|
||||
|
||||
https://www.hashicorp.com/integrations/circonus/nomad
|
||||
|
||||
#### Flowmill
|
||||
|
||||
https://www.flowmill.com/blog/announcing-flowmill-s-integration-with-nomad/
|
||||
|
||||
#### Sematext
|
||||
|
||||
https://www.hashicorp.com/integrations/sematext/nomad
|
||||
|
||||
#### Splunk
|
||||
|
||||
https://www.kmruddy.com/2020/deploying-splunk-enterprise-with-nomad/
|
||||
|
||||
### Secret Management
|
||||
|
||||
#### Vault
|
||||
|
||||
https://www.nomadproject.io/docs/integrations/vault-integration
|
||||
|
||||
### Service Mesh
|
||||
|
||||
#### Consul
|
||||
|
||||
https://www.nomadproject.io/docs/integrations/consul-integration
|
||||
|
||||
### Provisioning
|
||||
|
||||
#### Terraform
|
||||
|
||||
https://registry.terraform.io/providers/hashicorp/nomad/latest/docs
|
||||
|
||||
#### Chef
|
||||
|
||||
https://github.com/nathwill/chef-nomad
|
||||
|
||||
#### Ansible
|
||||
|
||||
https://github.com/ansible-community/ansible-nomad
|
||||
|
||||
### Cloud Native Network
|
||||
|
||||
#### CNI
|
||||
|
||||
https://www.nomadproject.io/docs/integrations/consul-connect#cni-plugins
|
||||
|
||||
### Service Proxy
|
||||
|
||||
#### Envoy
|
||||
|
||||
https://www.nomadproject.io/docs/integrations/consul-connect
|
||||
|
||||
#### NGINX
|
||||
|
||||
https://learn.hashicorp.com/tutorials/nomad/load-balancing-nginx
|
||||
|
||||
#### Traefik
|
||||
|
||||
https://learn.hashicorp.com/tutorials/nomad/load-balancing-traefik
|
||||
|
||||
### Storage
|
||||
|
||||
#### CSI
|
||||
|
||||
https://www.nomadproject.io/docs/internals/plugins/csi
|
||||
|
||||
#### Portworx
|
||||
|
||||
https://www.hashicorp.com/integrations/portworx/nomad
|
||||
|
||||
### GPUs
|
||||
|
||||
#### NVIDIA
|
||||
|
||||
https://developer.nvidia.com/blog/hashicorp-nomad-gpu-scheduling/
|
||||
|
||||
https://www.hashicorp.com/resources/running-gpu-accelerated-applications-on-nomad
|
||||
|
||||
### Autoscaling
|
||||
|
||||
#### AWS ASGs
|
||||
|
||||
Dynamically autoscale your Nomad clusters
|
||||
|
||||
https://www.hashicorp.com/blog/cluster-scaling-with-the-hashicorp-nomad-autoscaler
|
||||
|
||||
#### Spot
|
||||
|
||||
https://docs.spot.io/container-management/nomad/nomad-integration-with-elastigroup/
|
||||
42
website/pages/docs/nomad-vs-kubernetes/alternative.mdx
Normal file
42
website/pages/docs/nomad-vs-kubernetes/alternative.mdx
Normal file
@@ -0,0 +1,42 @@
|
||||
---
|
||||
layout: docs
|
||||
page_title: Alternative to Kubernetes
|
||||
sidebar_title: Alternative to Kubernetes
|
||||
description: Nomad as an alternative to Kubernetes
|
||||
---
|
||||
|
||||
# An alternative to Kubernetes
|
||||
|
||||
While known for its goal of automating and simplifying application deployment, an orchestrator itself can be extremely complex to implement and manage. Kubernetes requires significant time and deep understanding to deploy, operate, and troubleshoot. Teams and organizations choose Nomad as an alternative to Kubernetes for its two core strengths:
|
||||
|
||||
- **Simplicity in usage and maintainability**
|
||||
|
||||
- **Flexibility to deploy and manage containerized and non-containerized applications**
|
||||
|
||||
Operating as a single lightweight binary, Nomad excels on-premises and at the edge, providing the same ease-of-use as it does in the cloud. Its architectural simplicity, native federation capabilities, and operator-friendly design enable companies to scale and manage an orchestrator with little operational overhead. Our customer interviews show that no matter company size, teams and organizations gain benefits from simplicity and flexibility, including
|
||||
|
||||
- Fast time to production: Average 1-3 weeks to get Nomad from a technical proof of concept into production
|
||||
|
||||
- Rapid adoption: From 2 hours to less than 30 minutes to onboard a developer to directly deploy applications on Nomad
|
||||
|
||||
- Great operational efficiency: Allows operation teams to stay lean (1-4 people) to service hundreds of developers and applications, and achieve high uptime with a self-hosted orchestrator
|
||||
|
||||
- Smooth path to migration: Allows teams to incrementally migrate or containerize existing applications at their own pace with a single, unified deployment workflow
|
||||
|
||||
> “Nomad is easy to cluster up. We converted our Kubernetes deployment manifest to Nomad job files, then tested it. And since it’s a single binary, it’s simple to configure to our specific needs, which eliminates much of the complexity we faced with Kubernetes. More importantly, Nomad’s agnostic infrastructure resource pool and automated workflows let us deploy and manage our containers and apps across on-prem and any private or public cloud environment, which dramatically expands our datacenter options while still meeting our data residency obligations.”
|
||||
|
||||
**AmpleOrganics**, Canada's #1 cannabis software company migrated off of Kubernetes to Nomad
|
||||
|
||||
> “I’m a complete beginner when it comes to distributed computing and orchestration. Nomad virtually eliminates barriers to entry for developers who don’t have cloud computing expertise and makes it really easy to connect to the cluster, configure it, and run my jobs while having full visibility into the jobs’ status so I can restart them if need be.”
|
||||
|
||||
**Autodesk**, Autodesk Research built a scalable, maintenance-free, and multi-cloud orchestration workflow with Nomad
|
||||
|
||||
> “We have people who are first-time system administrators deploying applications, building containers, maintaining Nomad. There is a guy on our team who worked in the IT help desk for eight years — just today he upgraded an entire cluster himself. That’s the value proposition that I hope people understand. People seem to get stuck on ‘I need to run Kubernetes because my friend runs it’ — but do you really use it? Can you operate it at the level that’s needed?”
|
||||
|
||||
**Roblox**, the top online gaming company built a global gaming platform with Nomad serving more than 150 million players
|
||||
|
||||
> “A large portion of our applications are Windows-based, so we need both Windows and Linux support. Although we do prefer running containers, we don’t necessarily want a hard requirement to have to use them and we like the idea of directly running applications on VMs if the use case calls for it. We wanted to make improvements to the current workflow without massive and time-consuming application rewrites. Ultimately we chose Nomad because it met all of our requirements and made the most sense to our environments.”
|
||||
|
||||
**Q2** - The ebanking platform that serves 10% of the digital banking customers in America transformed the deployment workflow with Nomad
|
||||
|
||||
While Nomad’s strengths lie in simplicity and flexibility in core scheduling, Kubernetes excels over Nomad in terms of ecosystem. The goal for Nomad ecosystem is to build a simpler, leaner, and more prescriptive path to the ecosystem. This is an area of improvement for Nomad that we invest significantly in today and plan to continue into the future. [Read more about Nomad’s ecosystem](/docs/ecosystem).
|
||||
36
website/pages/docs/nomad-vs-kubernetes/index.mdx
Normal file
36
website/pages/docs/nomad-vs-kubernetes/index.mdx
Normal file
@@ -0,0 +1,36 @@
|
||||
---
|
||||
layout: docs
|
||||
page_title: Nomad vs. Kubernetes
|
||||
sidebar_title: Nomad vs. Kubernetes
|
||||
description: Comparison between Nomad and Kubernetes
|
||||
---
|
||||
|
||||
# Nomad vs. Kubernetes
|
||||
|
||||
Kubernetes is an orchestration system for containers originally designed by Google, now governed by the Cloud Native Computing Foundation (CNCF) and developed by Google, Red Hat, and many others. Kubernetes and Nomad support similar core use cases for application deployment and management, but they differ in a few key ways. Kubernetes aims to provide all the features needed to run Docker-based applications including cluster management, scheduling, service discovery, monitoring, secrets management and more. Nomad only aims to focus on cluster management and scheduling and is designed with the Unix philosophy of having a small scope while composing with tools like Consul for service discovery/service mesh and Vault for secret management.
|
||||
|
||||
The following characteristics generally differentiate Nomad from Kubernetes:
|
||||
|
||||
## Simplicity
|
||||
|
||||
Kubernetes is designed as a collection of more than a half-dozen interoperating services which together provide the full functionality. Coordination and storage is provided by etcd at the core. The state is wrapped by API controllers which are consumed by other services that provide higher level APIs for features like scheduling. Kubernetes supports running in a highly available configuration but is operationally complex to setup.
|
||||
|
||||
Nomad is architecturally much simpler. Nomad is a single binary, both for clients and servers, and requires no external services for coordination or storage. Nomad combines a lightweight resource manager and a sophisticated scheduler into a single system. By default, Nomad is distributed, highly available, and operationally simple.
|
||||
|
||||
## Flexible Workload Support
|
||||
|
||||
While Kubernetes is specifically focused on Docker, Nomad is more general purpose. Nomad supports virtualized, containerized and standalone applications, including Docker, Java, IIS on Windows, Qemu, etc. Nomad is designed with extensible drivers and support will be extended to all common drivers.
|
||||
|
||||
## Consistent Deployment
|
||||
|
||||
A full Kubernetes installation for a production environment is time consuming, operationally complex, and resource intensive. An increasing number of implementations are created by the Kubernetes community to mitigate these challenges, such as minikube, kubeadm, k3s, and more. These trimmed versions of Kubernetes offer easier adoption for development and testing, but lead to inconsistency in capabilities, configuration, and management when moving into production.
|
||||
|
||||
In contrast to Kuberentes' fragmented distributions, Nomad as a single lightweight binary can be deployed in local dev, production, on-prem, at the edge, and in the cloud in a consistent manner, and provides the same operational ease-of-use across all environments.
|
||||
|
||||
## Scalability
|
||||
|
||||
[Kubernetes documentation](https://kubernetes.io/docs/setup/best-practices/cluster-large/) states that they support clusters up to 5,000 nodes and 300,000 total containers. As the environment grows, the interoperating components with different constraints compound the operational complexity. [Even operators at Google revealed the significant challenges of managing the system at scale](https://blog.dave.tf/post/new-kubernetes/). The lack of maturity in the Federation project and the additional overhead of managing a centralized management plane also make it a hard experience to deploy a distributed system that spans multiple clusters.
|
||||
|
||||
Nomad has been proven to scale to cluster sizes that exceed 10,000 nodes in real-world production environments. It can be deployed across multiple availability zones, regions, and data centers with a single cluster or multiple clusters. Nomad is designed to natively handle multi-cluster deployments without the overhead of running clusters on clusters. This makes it easier to scale the application deployment across multiple datacenters, regions, and clouds with no additional complexity.
|
||||
|
||||
Nomad has performed strenuous benchmark on scalability with [1 million container challenge](https://www.hashicorp.com/c1m) in 2016 and [2 million container challenge](https://www.hashicorp.com/c2m) in 2020. These tests are aimed to validate Nomad's architectural design and ensure that Nomad performs under the most extreme requirements.
|
||||
42
website/pages/docs/nomad-vs-kubernetes/supplement.mdx
Normal file
42
website/pages/docs/nomad-vs-kubernetes/supplement.mdx
Normal file
@@ -0,0 +1,42 @@
|
||||
---
|
||||
layout: docs
|
||||
page_title: Supplement to Kubernetes
|
||||
sidebar_title: Supplement to Kubernetes
|
||||
description: Comparison between Nomad and Kubernetes
|
||||
---
|
||||
|
||||
# Supplement to Kubernetes
|
||||
|
||||
Enterprises are comprised of multiple groups of people (business units) with different projects, infrastructure environments, technical competencies, team sizes, budgets, and SLAs. Each group has different requirements and leverages technologies based on their particular needs and constraints.
|
||||
|
||||
Medium to large scale enterprises run into challenges when trying to standardize hundreds to thousands of software developers and administrators onto one single orchestrator (Kubernetes, Nomad, Mesos) as no scheduler today fits all applications, environments, projects, and teams.
|
||||
|
||||
Companies in the Global 2000 today such as Intel, Autodesk and Github with multiple products and business units organically run Nomad and Kubernetes to supplement each other. They leverage each scheduler to its strengths with Kubernetes for its cutting edge ecosystem and Nomad for simple maintenance and flexibility in core scheduling.
|
||||
|
||||
|
||||
|
||||
These are the characteristics we see in teams that typically adopt self-hosted Kubernetes:
|
||||
|
||||
- Greenfield use-cases such as machine learning (ML), serverless, and big data that require the Kubernetes ecosystem and Helm chart
|
||||
|
||||
- High budget and full-time staffing to maintain Kubernetes
|
||||
|
||||
- High-profile projects with significant investment and long-term timeline (multi-year)
|
||||
|
||||
- Deploying and managing new, cloud-native applications
|
||||
|
||||
- Public cloud environment such as AWS, GCP, Azure
|
||||
|
||||
Characteristics of teams that typically adopt Nomad:
|
||||
|
||||
- Run a mix of containerized and non-containerized workloads (Windows, Java)
|
||||
|
||||
- Small/medium-sized teams with limited capacity to maintain an orchestrator
|
||||
|
||||
- Deploying and managing core, existing applications
|
||||
|
||||
- On-premises environment, or hybrid environments
|
||||
|
||||
- Require simplicity to move fast and fulfill business needs with hard deadlines
|
||||
|
||||
We continue to see small enterprises continue to standardize on a single orchestrator given the natural staffing and organizational constraints. There are not enough DevOps members to maintain more than one orchestrator, not enough developers to warrant diverging workflows, or simply not enough workload diversity to require more than one orchestrator.
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
layout: intro
|
||||
layout: docs
|
||||
page_title: Who Uses Nomad
|
||||
sidebar_title: Who Uses Nomad
|
||||
description: >-
|
||||
@@ -29,6 +29,8 @@ export default function Homepage() {
|
||||
|
||||
<FeaturesList
|
||||
title="Why Nomad?"
|
||||
intro="Nomad is widely adopted and used in production by organizations in traditional on-premises datacenters, at the edge, and on the cloud. Learn why users choose Nomad as an <a href='/docs/nomad-vs-kubernetes'>alternative to Kubernetes.</a>
|
||||
"
|
||||
items={[
|
||||
{
|
||||
title: 'Simple and Lightweight',
|
||||
|
||||
@@ -1,39 +0,0 @@
|
||||
---
|
||||
layout: intro
|
||||
page_title: Nomad vs. Kubernetes
|
||||
sidebar_title: Kubernetes
|
||||
description: Comparison between Nomad and Kubernetes
|
||||
---
|
||||
|
||||
# Nomad vs. Kubernetes
|
||||
|
||||
Kubernetes is an orchestration system for containers originally designed by Google, now governed by the Cloud Native
|
||||
Computing Foundation (CNCF) and developed by Google, Red Hat, CoreOS and many others. Kubernetes aims to provide all the features needed to run Docker or Rkt-based applications including cluster management,
|
||||
scheduling, service discovery, monitoring, secrets management and more.
|
||||
|
||||
Nomad only aims to provide cluster management and scheduling and is designed
|
||||
with the Unix philosophy of having a small scope while composing with tools like [Consul](https://www.consul.io)
|
||||
for service discovery and [Vault](https://www.vaultproject.io) for secret management.
|
||||
|
||||
While Kubernetes is specifically focused on Docker, Nomad is more general purpose.
|
||||
Nomad supports virtualized, containerized and standalone applications, including Docker.
|
||||
Nomad is designed with extensible drivers and support will be extended to all
|
||||
common drivers.
|
||||
|
||||
Kubernetes is designed as a collection of more than a half-dozen interoperating
|
||||
services which together provide the full functionality. Coordination and
|
||||
storage is provided by etcd at the core. The state is wrapped by API controllers
|
||||
which are consumed by other services that provide higher level APIs for features
|
||||
like scheduling. Kubernetes supports running in a highly available
|
||||
configuration but is operationally complex to setup.
|
||||
|
||||
Nomad is architecturally much simpler. Nomad is a single binary, both for clients
|
||||
and servers, and requires no external services for coordination or storage.
|
||||
Nomad combines a lightweight resource manager and a sophisticated scheduler
|
||||
into a single system. By default, Nomad is distributed, highly available,
|
||||
and operationally simple.
|
||||
|
||||
Kubernetes documentation states they can support clusters greater than 5,000 nodes
|
||||
and they support a multi-AZ/multi-region configuration. Nomad has been proven to scale
|
||||
to cluster sizes that exceed 10,000 nodes in real-world production environments. Nomad
|
||||
also natively supports multi-datacenter and multi-region configurations.
|
||||
@@ -1,356 +0,0 @@
|
||||
import Head from 'next/head'
|
||||
import HashiHead from '@hashicorp/react-head'
|
||||
import Content from '@hashicorp/react-content'
|
||||
|
||||
export default function ResourcesPage() {
|
||||
return (
|
||||
<>
|
||||
<HashiHead
|
||||
is={Head}
|
||||
title="Community | Nomad by HashiCorp"
|
||||
description="Nomad is widely deployed across a range of enterprises and business verticals."
|
||||
/>
|
||||
<div id="p-resources" className="g-grid-container">
|
||||
<Content
|
||||
product="nomad"
|
||||
content={
|
||||
<>
|
||||
<h2>Community</h2>
|
||||
<p>
|
||||
Nomad is widely adopted and used in production by organizations
|
||||
like Cloudflare, Roblox, Pandora, PagerDuty, and more.
|
||||
</p>
|
||||
<p>
|
||||
This is a collection of resources for joining our community and
|
||||
learning Nomad's real world use-cases.
|
||||
</p>
|
||||
<p>
|
||||
<strong>Discussion Forum</strong>
|
||||
<ul>
|
||||
<li>
|
||||
<a href="https://discuss.hashicorp.com/c/nomad">
|
||||
HashiCorp Discuss
|
||||
</a>
|
||||
</li>
|
||||
</ul>
|
||||
</p>
|
||||
<p>
|
||||
<strong>Virtual Talks</strong>
|
||||
<ul>
|
||||
<li>
|
||||
<a href="https://www.hashicorp.com/resources/nomad-scheduling-101-why-let-container-runtimes-have-all-the-fun/">
|
||||
6/9 Scheduling Containers, .NET, Java Applications with
|
||||
Nomad (2020)
|
||||
</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href="https://www.hashicorp.com/resources/nomad-ci-cd-developer-workflows-and-integrations/">
|
||||
5/29 Build a CI/CD Pipeline with Nomad & Gitlab (2020)
|
||||
</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href="https://www.hashicorp.com/resources/cloud-bursting-made-real-with-nomad-and-consul/">
|
||||
5/29 Cloud Bursting Demo with Nomad & Consul (2020)
|
||||
</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href="https://www.hashicorp.com/resources/nomad-expert-panel-live-q2-2020/">
|
||||
5/29 Nomad Expert Panel Live Q&A (2020)
|
||||
</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href="https://www.hashicorp.com/resources/governance-for-multiple-teams-sharing-a-nomad-cluster/">
|
||||
5/15 Governance for Multiple Teams Sharing a Nomad Cluster
|
||||
(2020)
|
||||
</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href="https://www.hashicorp.com/resources/modern-scheduling-for-modern-applications-with-nomad/">
|
||||
{' '}
|
||||
4/20 Modern Scheduling for Modern Applications with Nomad
|
||||
(2020)
|
||||
</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href="https://www.hashicorp.com/resources/solutions-engineering-hangout-integrating-nomad-with-vault/">
|
||||
{' '}
|
||||
4/17 Integrating Nomad with Vault Demo (2020)
|
||||
</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href="https://www.hashicorp.com/resources/nomad-tech-deep-dive-autoscaling-csi-plugins-and-more/">
|
||||
4/14 Nomad Deep Dive: Autoscaling, CSI Plugins, and More
|
||||
(2020)
|
||||
</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href="https://www.hashicorp.com/resources/nomad-virtual-day-2020-panel-discussion/">
|
||||
3/16 Nomad Panel Discussion with Roblox (2020)
|
||||
</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href="https://www.hashicorp.com/resources/hashicorp-nomad-vs-kubernetes-comparing-complexity/">
|
||||
3/3 Nomad vs. Kubernetes - Comparing Complexity (2020)
|
||||
</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href="https://www.hashicorp.com/resources/ground-control-to-nomad-job-dispatch/">
|
||||
2/27 Ground Control to Nomad Job Dispatch (2020)
|
||||
</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href="https://www.hashicorp.com/resources/nomad-best-practices-for-reliable-deploys/">
|
||||
2/27 Best Practices for Reliable Deploys on Nomad (2020)
|
||||
</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href="https://www.hashicorp.com/resources/monitoring-nomad-with-prometheus-and-icinga/">
|
||||
2/27 Monitoring Nomad with Prometheus and Incinga (2020)
|
||||
</a>
|
||||
</li>
|
||||
</ul>
|
||||
</p>
|
||||
<p>
|
||||
<strong>Bug Tracker</strong>
|
||||
<ul>
|
||||
<li>
|
||||
<a href="https://github.com/hashicorp/nomad/issues">
|
||||
GitHub Issues
|
||||
</a>
|
||||
</li>
|
||||
</ul>
|
||||
Please only use this to report bugs. For general help, please
|
||||
use our <a href="https://discuss.hashicorp.com/c/nomad">discussion forum</a>.
|
||||
</p>
|
||||
<h3>Who Uses Nomad</h3>
|
||||
<h4>Roblox</h4>
|
||||
<ul>
|
||||
<li>
|
||||
<a href="https://www.hashicorp.com/case-studies/roblox/">
|
||||
How Roblox built a platform for 100 million players on Nomad
|
||||
(2020)
|
||||
</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href="https://portworx.com/architects-corner-roblox-runs-platform-70-million-gamers-hashicorp-nomad/">
|
||||
How Roblox built a platform for 70 million gamers on Nomad
|
||||
(2019)
|
||||
</a>
|
||||
</li>
|
||||
</ul>
|
||||
<h4>Cloudflare</h4>
|
||||
<ul>
|
||||
<li>
|
||||
<a href="https://blog.cloudflare.com/how-we-use-hashicorp-nomad/">
|
||||
How Cloudflare Uses HashiCorp Nomad (2020)
|
||||
</a>
|
||||
</li>
|
||||
</ul>
|
||||
<h4>BetterHelp</h4>
|
||||
<ul>
|
||||
<li>
|
||||
<a href="https://www.youtube.com/watch?v=eN2ghrGpiUo">
|
||||
How the world's largest online therapy provider runs on
|
||||
Nomad (2020)
|
||||
</a>
|
||||
</li>
|
||||
</ul>
|
||||
<h4>Navi Capital</h4>
|
||||
<ul>
|
||||
<li>
|
||||
<a href="https://www.hashicorp.com/blog/nomad-community-story-navi-capital/">
|
||||
How Nomad powers a $1B hedge fund in Brazil (2020)
|
||||
</a>
|
||||
</li>
|
||||
</ul>
|
||||
<h4>Trivago</h4>
|
||||
<ul>
|
||||
<li>
|
||||
<a href="https://endler.dev/2019/maybe-you-dont-need-kubernetes/">
|
||||
Maybe You Don't Need Kubernetes (2019)
|
||||
</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href="https://tech.trivago.com/2019/01/25/nomad-our-experiences-and-best-practices/">
|
||||
Nomad - Our Experiences and Best Practices (2019)
|
||||
</a>
|
||||
</li>
|
||||
</ul>
|
||||
<h4>Reaktor</h4>
|
||||
<ul>
|
||||
<li>
|
||||
<a href="https://youtu.be/GkmyNBUugg8">
|
||||
Nomad: Kubernetes, but without the complexity (2019)
|
||||
</a>
|
||||
</li>
|
||||
</ul>
|
||||
<h4>Pandora</h4>
|
||||
<ul>
|
||||
<li>
|
||||
<a href="https://www.youtube.com/watch?v=OsZeKTP2u98&t=2s">
|
||||
How Pandora Uses Nomad (2019)
|
||||
</a>
|
||||
</li>
|
||||
</ul>
|
||||
<h4>CircleCI</h4>
|
||||
<ul>
|
||||
<li>
|
||||
<a href="https://stackshare.io/circleci/how-circleci-processes-4-5-million-builds-per-month">
|
||||
{' '}
|
||||
How CircleCI Processes 4.5 Million Builds Per Month with
|
||||
Nomad (2019)
|
||||
</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href="https://www.hashicorp.com/resources/nomad-vault-circleci-security-scheduling">
|
||||
{' '}
|
||||
Security & Scheduling Are Not Your Core Competencies (2018)
|
||||
</a>
|
||||
</li>
|
||||
</ul>
|
||||
<h4>Q2</h4>
|
||||
<ul>
|
||||
<li>
|
||||
<a href="https://www.youtube.com/watch?v=OsZeKTP2u98&feature=youtu.be&t=1499">
|
||||
{' '}
|
||||
Q2's Nomad Use and Overview (2019)
|
||||
</a>
|
||||
</li>
|
||||
</ul>
|
||||
<h4>Deluxe Entertainment</h4>
|
||||
<ul>
|
||||
<li>
|
||||
<a href="https://www.hashicorp.com/resources/deluxe-hashistack-video-production">
|
||||
{' '}
|
||||
How We Use the HashiStack for Video Production (2018)
|
||||
</a>
|
||||
</li>
|
||||
</ul>
|
||||
<h4>SAP</h4>
|
||||
<ul>
|
||||
<li>
|
||||
<a href="https://www.hashicorp.com/resources/nomad-community-call-core-team-sap-ariba">
|
||||
How We Use Nomad @ SAP Ariba (2018)
|
||||
</a>
|
||||
</li>
|
||||
</ul>
|
||||
<h4>PagerDuty</h4>
|
||||
<ul>
|
||||
<li>
|
||||
<a href="https://www.hashicorp.com/resources/pagerduty-nomad-journey">
|
||||
PagerDuty's Nomadic Journey (2017)
|
||||
</a>
|
||||
</li>
|
||||
</ul>
|
||||
<h4>Target</h4>
|
||||
<ul>
|
||||
<li>
|
||||
<a href="https://www.hashicorp.com/resources/nomad-scaling-target-microservices-across-cloud">
|
||||
{' '}
|
||||
Nomad at Target: Scaling Microservices Across Public and
|
||||
Private Clouds (2018)
|
||||
</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href="https://danielparker.me/nomad/hashicorp/schedulers/nomad/">
|
||||
{' '}
|
||||
Playing with Nomad from HashiCorp (2017)
|
||||
</a>
|
||||
</li>
|
||||
</ul>
|
||||
<h4>Oscar Health</h4>
|
||||
<ul>
|
||||
<li>
|
||||
<a href="https://www.hashicorp.com/resources/scalable-ci-oscar-health-insurance-nomad-docker">
|
||||
Scalable CI at Oscar Health with Nomad and Docker (2018)
|
||||
</a>
|
||||
</li>
|
||||
</ul>
|
||||
<h4>eBay</h4>
|
||||
<ul>
|
||||
<li>
|
||||
<a href="https://www.hashicorp.com/resources/ebay-hashistack-fully-containerized-platform-iac">
|
||||
HashiStack at eBay: A Fully Containerized Platform Based on
|
||||
Infrastructure as Code (2018)
|
||||
</a>
|
||||
</li>
|
||||
</ul>
|
||||
<h4>Dutch National Police</h4>
|
||||
<ul>
|
||||
<li>
|
||||
<a href="https://www.hashicorp.com/resources/going-cloud-native-at-the-dutch-national-police">
|
||||
Going Cloud-Native at the Dutch National Police (2018)
|
||||
</a>
|
||||
</li>
|
||||
</ul>
|
||||
<h4>N26</h4>
|
||||
<ul>
|
||||
<li>
|
||||
<a href="https://medium.com/insiden26/tech-at-n26-the-bank-in-the-cloud-e5ff818b528b">
|
||||
Tech at N26 - The Bank in the Cloud (2018)
|
||||
</a>
|
||||
</li>
|
||||
</ul>
|
||||
<h4>NIH NCBI</h4>
|
||||
<ul>
|
||||
<li>
|
||||
<a href="https://www.hashicorp.com/resources/ncbi-legacy-migration-hybrid-cloud-consul-nomad">
|
||||
NCBI's Legacy Migration to Hybrid Cloud with Nomad & Consul
|
||||
(2018)
|
||||
</a>
|
||||
</li>
|
||||
</ul>
|
||||
<h4>Citadel</h4>
|
||||
<ul>
|
||||
<li>
|
||||
<a href="https://www.hashicorp.com/resources/end-to-end-production-nomad-citadel">
|
||||
End-to-End Production Nomad at Citadel (2017)
|
||||
</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href="https://www.hashicorp.com/resources/citadel-scaling-hashicorp-nomad-consul">
|
||||
Extreme Scaling with HashiCorp Nomoad & Consul (2016)
|
||||
</a>
|
||||
</li>
|
||||
</ul>
|
||||
<h4>Jet.com</h4>
|
||||
<ul>
|
||||
<li>
|
||||
<a href="https://www.hashicorp.com/resources/jet-walmart-hashicorp-nomad-azure-run-apps">
|
||||
Driving down costs at Jet.com with HashiCorp Nomad (2017)
|
||||
</a>
|
||||
</li>
|
||||
</ul>
|
||||
<h4>Elsevier</h4>
|
||||
<ul>
|
||||
<li>
|
||||
<a href="https://www.hashicorp.com/resources/elsevier-nomad-container-framework-demo">
|
||||
Elsevier's Container Framework with Nomad, Terraform, and
|
||||
Consul (2017)
|
||||
</a>
|
||||
</li>
|
||||
</ul>
|
||||
<h4>Graymeta</h4>
|
||||
<ul>
|
||||
<li>
|
||||
<a href="https://www.hashicorp.com/resources/backend-batch-processing-nomad">
|
||||
Backend Batch Process at Scale with Nomad (2017)
|
||||
</a>
|
||||
</li>
|
||||
</ul>
|
||||
<h4>imigx</h4>
|
||||
<ul>
|
||||
<li>
|
||||
<a href="https://medium.com/@copyconstruct/schedulers-kubernetes-and-nomad-b0f2e14a896">
|
||||
Cluster Schedulers & Why We Chose Nomad over Kubernetes
|
||||
(2017)
|
||||
</a>
|
||||
</li>
|
||||
</ul>
|
||||
</>
|
||||
}
|
||||
/>
|
||||
</div>
|
||||
</>
|
||||
)
|
||||
}
|
||||
@@ -54,7 +54,7 @@
|
||||
@import './home/style.css';
|
||||
@import './downloads/style.css';
|
||||
@import './security/style.css';
|
||||
@import './resources/style.css';
|
||||
@import './community/style.css';
|
||||
@import '../layouts/use-cases/style.css';
|
||||
|
||||
/* Print Styles */
|
||||
|
||||
@@ -18,6 +18,11 @@ module.exports = [
|
||||
},
|
||||
|
||||
// Nomad Learn Redirects
|
||||
{
|
||||
source: '/intro/getting-started',
|
||||
destination: 'https://learn.hashicorp.com/collections/nomad/get-started',
|
||||
permanent: true,
|
||||
},
|
||||
{
|
||||
source: '/intro/getting-started/install',
|
||||
destination:
|
||||
@@ -51,7 +56,17 @@ module.exports = [
|
||||
'https://learn.hashicorp.com/tutorials/nomad/get-started-learn-more',
|
||||
permanent: true,
|
||||
},
|
||||
|
||||
{
|
||||
source: '/intro/vs/kubernetes',
|
||||
destination: '/docs/nomad-vs-kubernetes',
|
||||
permanent: true,
|
||||
},
|
||||
{
|
||||
source: '/intro/who-uses-nomad',
|
||||
destination: '/docs/who-uses/noamd',
|
||||
permanent: true,
|
||||
},
|
||||
// Guides
|
||||
{
|
||||
source: '/guides/load-balancing',
|
||||
destination: 'https://learn.hashicorp.com/collections/nomad/load-balancing',
|
||||
@@ -413,12 +428,6 @@ module.exports = [
|
||||
},
|
||||
|
||||
// Website
|
||||
{
|
||||
source: '/community',
|
||||
destination: '/resources',
|
||||
permanent: true,
|
||||
},
|
||||
|
||||
// Docs
|
||||
{
|
||||
source: '/docs/index',
|
||||
@@ -1211,7 +1220,12 @@ module.exports = [
|
||||
destination: '/docs/integrations/vault-integration',
|
||||
permanent: true,
|
||||
},
|
||||
|
||||
// Old resources -> Community
|
||||
{
|
||||
source: '/resources',
|
||||
destination: '/community',
|
||||
permanent: true,
|
||||
},
|
||||
// `/<path>/index.html` to /<path>
|
||||
{
|
||||
source: '/:splat*/index.html',
|
||||
|
||||
Reference in New Issue
Block a user