index.xml

<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Huan Zhang&#39;s blog</title>
    <link>https://fisher046.github.io/</link>
    <description>Recent content on Huan Zhang&#39;s blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Fri, 08 Mar 2019 09:05:12 +0800</lastBuildDate>
    
	<atom:link href="https://fisher046.github.io/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>How to generate kubeconfig with limited access</title>
      <link>https://fisher046.github.io/post/how-to-generate-kube-config-with-limited-access/</link>
      <pubDate>Fri, 08 Mar 2019 09:05:12 +0800</pubDate>
      
      <guid>https://fisher046.github.io/post/how-to-generate-kube-config-with-limited-access/</guid>
      <description>Requirement I have full access kubeconfig and I want to provide a limited kubeconfig to another user, which only has access to resources in one specific namespace.
Steps Create the namespace.
1  kubectl create namespace example   Create a ServiceAccount in previous namespace.
1 2 3 4 5  apiVersion:v1kind:ServiceAccountmetadata:name:example-usernamespace:example  1  kubectl create -f service_account.yaml   Create Role and RoleBinding for the ServiceAccount in previous namespace.</description>
    </item>
    
    <item>
      <title>How to create PV dynamically on k8s with AWS EFS</title>
      <link>https://fisher046.github.io/post/how-to-create-pv-dynamically-on-k8s-with-aws-efs/</link>
      <pubDate>Tue, 05 Mar 2019 09:36:00 +0800</pubDate>
      
      <guid>https://fisher046.github.io/post/how-to-create-pv-dynamically-on-k8s-with-aws-efs/</guid>
      <description>Preface When I was using AWS as Kubernetes cloud provider, I have two choices for persistent volume, EBS and EFS. However, EBS can only mount to one EC2 instance, which is not appropriate to my scenario, so I can only choose EFS.
My requirement is that when I need a persistent volume, I only create PVC and the related PV should be created automatically. So I summary the steps to reach my purpose in below words.</description>
    </item>
    
    <item>
      <title>Tips of deploying service on Kubernetes</title>
      <link>https://fisher046.github.io/post/tips-of-deploying-service-on-k8s/</link>
      <pubDate>Sun, 21 Oct 2018 13:35:00 +0800</pubDate>
      
      <guid>https://fisher046.github.io/post/tips-of-deploying-service-on-k8s/</guid>
      <description>Preface These are some tips or something should be considered when you want to deploy your service on Kubernetes.
About Pod How to decide what things should be put in one Pod? When designing a Pod, you should consider below 4 types container.
 Function container Init container Monitor container Operator container     Function container is the service.
Init container is responsible for initializing the service. For example, the configuration.</description>
    </item>
    
    <item>
      <title>Understanding the nil in Golang</title>
      <link>https://fisher046.github.io/post/understanding-the-nil-in-golang/</link>
      <pubDate>Fri, 10 Aug 2018 17:00:00 +0800</pubDate>
      
      <guid>https://fisher046.github.io/post/understanding-the-nil-in-golang/</guid>
      <description>Reference GopherCon 2016: Francesc Campoy - Understanding nil 理解Go语言的nil Is it a bug? 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 package main import ( &amp;#34;fmt&amp;#34; ) type doError struct{} func (e *doError) Error() string { return &amp;#34;&amp;#34; } func do() error { var err *doError return err</description>
    </item>
    
  </channel>
</rss>