anchor.diff:      secretName: gocd-server-ssh
   ~~~
   
  -##Configuring Access to GitHub for GoCD Agent
  +##**Configuring Access to GitHub for GoCD Agent**
   
   Just because the GoCD Server has access doesn’t mean that it’s corresponding GoCD agents will also have access. Access for agents has to be configured separately. This is similar to configuring for the server. You can specify the secret name in the *agent.security.ssh* section as follows
   
  
positive.code: ---
  layout: post
  title: Use OpenLDAP for User Authentication in GoCD
  type: post
  author: Mohamed Najiullah
  excerpt: "Understand more about how to use OpenLDAP and authenticate and scale your users in GoCD"
  summary_image: "/assets/images/blog/cd-hacks/open-ldap-gocd.jpg"
  title_tag_of_header: "OpenLDAP for User Authentication in GoCD | GoCD Blog"
  meta_description: "Understand more about how to use OpenLDAP and authenticate and scale your users in GoCD"
  meta_keywords: "ldap, openldap, user authentication, ci cd, authenticate users, active directory"
  tags: CD Hacks
  draft: true
  ---
  <% content_for :banner do %>
  
negative.code: 
  This will install *Tiller* which is the server side component of Helm on your cluster.
  
  3) Next we need to create a cluster role binding with the kube-system service account.
  
  ~~~
  kubectl create clusterrolebinding clusterRoleBinding \
  