<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Rancher on Wenhan blog</title>
    <link>https://wenhan.blog/en/tags/rancher/</link>
    <description>Recent content in Rancher on Wenhan blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-US</language>
    <lastBuildDate>Wed, 26 Jan 2022 11:33:00 +0900</lastBuildDate><atom:link href="https://wenhan.blog/en/tags/rancher/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Cause and Fix for --node-cidr-mask-size Error</title>
      <link>https://wenhan.blog/en/posts/20220126_--node-cidr-mask-size_error/</link>
      <pubDate>Wed, 26 Jan 2022 11:33:00 +0900</pubDate>
      
      <guid>https://wenhan.blog/en/posts/20220126_--node-cidr-mask-size_error/</guid>
      <description>When I changed the CIDR of an rke cluster, I encountered the following error and the cluster creation failed.
1 {&amp;#34;log&amp;#34;:&amp;#34;F1203 01:36:22.168496 1 node_ipam_controller.go:115] Controller: Invalid --cluster-cidr, mask size of cluster CIDR must be less than or equal to --node-cidr-mask-size configured for CIDR family\n&amp;#34;,&amp;#34;stream&amp;#34;:&amp;#34;stderr&amp;#34;,&amp;#34;time&amp;#34;:&amp;#34;2021-12-03T01:36:22.16859524Z&amp;#34;} The relevant part of cluster.yaml is as follows:
1 2 3 4 5 6 services: kube-controller: cluster_cidr: 10.42.0.0/25 service_cluster_ip_range: 10.43.0.0/25 kube-api: service_cluster_ip_range: 10.43.0.0/25 The problematic part is the mask size of the CIDR.</description>
    </item>
    
    <item>
      <title>Achieve Easy GitOps with Rancher&#39;s Continuous Delivery Feature</title>
      <link>https://wenhan.blog/en/posts/20211111_fleet-demo/</link>
      <pubDate>Thu, 11 Nov 2021 16:18:38 +0900</pubDate>
      
      <guid>https://wenhan.blog/en/posts/20211111_fleet-demo/</guid>
      <description>This article builds a single-node Rancher server and two k3s cluster environments, and uses Rancher&amp;rsquo;s Continuous Delivery feature to operate both k3s clusters via GitOps.
Step 1: Deploying a Rancher Server First, on the rancher node, run the following docker command to set up a single-node Rancher server.
1 2 3 4 sudo docker run -d --restart=unless-stopped \ -p 80:80 -p 443:443 \ --privileged \ rancher/rancher:v2.5.10 The Rancher server will start in about a minute.</description>
    </item>
    
  </channel>
</rss>
