Eslatma. tarjima.: Operatorlar Kubernetes uchun yordamchi dasturiy ta'minot bo'lib, ma'lum hodisalar sodir bo'lganda klaster ob'ektlarida muntazam harakatlarni bajarishni avtomatlashtirish uchun mo'ljallangan. Biz allaqachon operatorlar haqida yozgan edik
Kodni o'rganishdan o'tgan Kubernetes uchun operator yaratish bo'yicha hujjatlarni topishga urinishlarimdan so'ng, men ushbu postni hayotiy misol bilan yozishga qaror qildim.
Ta'riflanadigan misol bu: bizning Kubernetes klasterimizda, har biri Namespace
jamoaning sandbox muhitini ifodalaydi va biz ularga kirishni cheklashni xohladik, shunda jamoalar faqat o'zlarining sandboxlarida o'ynashlari mumkin.
Foydalanuvchiga guruhni tayinlash orqali siz xohlagan narsangizga erishishingiz mumkin RoleBinding
aniqlikka Namespace
ΠΈ ClusterRole
tahrir qilish huquqi bilan. YAML taqdimoti quyidagicha ko'rinadi:
---
kind: RoleBinding
apiVersion: rbac.authorization.k8s.io/v1beta1
metadata:
name: kubernetes-team-1
namespace: team-1
subjects:
- kind: Group
name: kubernetes-team-1
apiGroup: rbac.authorization.k8s.io
roleRef:
kind: ClusterRole
name: edit
apiGroup: rbac.authorization.k8s.io
(
Bir yarating RoleBinding
Siz buni qo'lda qilishingiz mumkin, lekin yuzta nom maydoni belgisini kesib o'tganingizdan so'ng, bu zerikarli vazifaga aylanadi. Bu erda Kubernetes operatorlari yordam beradi β ular resurslarga o'zgartirishlar asosida Kubernetes resurslarini yaratishni avtomatlashtirish imkonini beradi. Bizning holatlarimizda biz yaratmoqchimiz RoleBinding
yaratish paytida Namespace
.
Avvalo, funksiyani aniqlaymiz main
bayonotni ishga tushirish uchun kerakli sozlashni amalga oshiradi va keyin bayonot harakatini chaqiradi:
(Eslatma. tarjima.: bu yerda va quyida koddagi izohlar rus tiliga tarjima qilingan. Bundan tashqari, chekinish faqat Habr tartibida yaxshiroq o'qilishi uchun [O'tish-da tavsiya etilgan] yorliqlari o'rniga bo'shliqlarga tuzatildi. Har bir ro'yxatdan so'ng GitHub-da ingliz tilidagi sharhlar va yorliqlar saqlanadigan asl nusxaga havolalar mavjud.)
func main() {
// Π£ΡΡΠ°Π½Π°Π²Π»ΠΈΠ²Π°Π΅ΠΌ Π²ΡΠ²ΠΎΠ΄ Π»ΠΎΠ³ΠΎΠ² Π² ΠΊΠΎΠ½ΡΠΎΠ»ΡΠ½ΡΠΉ STDOUT
log.SetOutput(os.Stdout)
sigs := make(chan os.Signal, 1) // Π‘ΠΎΠ·Π΄Π°Π΅ΠΌ ΠΊΠ°Π½Π°Π» Π΄Π»Ρ ΠΏΠΎΠ»ΡΡΠ΅Π½ΠΈΡ ΡΠΈΠ³Π½Π°Π»ΠΎΠ² ΠΠ‘
stop := make(chan struct{}) // Π‘ΠΎΠ·Π΄Π°Π΅ΠΌ ΠΊΠ°Π½Π°Π» Π΄Π»Ρ ΠΏΠΎΠ»ΡΡΠ΅Π½ΠΈΡ ΡΡΠΎΠΏ-ΡΠΈΠ³Π½Π°Π»Π°
// Π Π΅Π³ΠΈΡΡΡΠΈΡΡΠ΅ΠΌ ΠΏΠΎΠ»ΡΡΠ΅Π½ΠΈΠ΅ SIGTERM Π² ΠΊΠ°Π½Π°Π»Π΅ sigs
signal.Notify(sigs, os.Interrupt, syscall.SIGTERM, syscall.SIGINT)
// Goroutines ΠΌΠΎΠ³ΡΡ ΡΠ°ΠΌΠΈ Π΄ΠΎΠ±Π°Π²Π»ΡΡΡ ΡΠ΅Π±Ρ Π² WaitGroup,
// ΡΡΠΎΠ±Ρ Π·Π°Π²Π΅ΡΡΠ΅Π½ΠΈΡ ΠΈΡ
Π²ΡΠΏΠΎΠ»Π½Π΅Π½ΠΈΡ Π΄ΠΎΠΆΠΈΠ΄Π°Π»ΠΈΡΡ
wg := &sync.WaitGroup{}
runOutsideCluster := flag.Bool("run-outside-cluster", false, "Set this flag when running outside of the cluster.")
flag.Parse()
// Π‘ΠΎΠ·Π΄Π°Π΅ΠΌ clientset Π΄Π»Ρ Π²Π·Π°ΠΈΠΌΠΎΠ΄Π΅ΠΉΡΡΠ²ΠΈΡ Ρ ΠΊΠ»Π°ΡΡΠ΅ΡΠΎΠΌ Kubernetes
clientset, err := newClientSet(*runOutsideCluster)
if err != nil {
panic(err.Error())
}
controller.NewNamespaceController(clientset).Run(stop, wg)
<-sigs // ΠΠ΄Π΅ΠΌ ΡΠΈΠ³Π½Π°Π»ΠΎΠ² (Π΄ΠΎ ΠΏΠΎΠ»ΡΡΠ΅Π½ΠΈΡ ΡΠΈΠ³Π½Π°Π»Π° Π±ΠΎΠ»Π΅Π΅ Π½ΠΈΡΠ΅Π³ΠΎ Π½Π΅ ΠΏΡΠΎΠΈΡΡ
ΠΎΠ΄ΠΈΡ)
log.Printf("Shutting down...")
close(stop) // ΠΠΎΠ²ΠΎΡΠΈΠΌ goroutines ΠΎΡΡΠ°Π½ΠΎΠ²ΠΈΡΡΡΡ
wg.Wait() // ΠΠΆΠΈΠ΄Π°Π΅ΠΌ, ΡΡΠΎ Π²ΡΠ΅ ΠΎΡΡΠ°Π½ΠΎΠ²Π»Π΅Π½ΠΎ
}
Biz quyidagilarni bajaramiz:
- Operatorni oqilona tugatishga olib keladigan muayyan operatsion tizim signallari uchun ishlov beruvchini sozlaymiz.
- Biz foydalanamiz
WaitGroup
ilovani tugatishdan oldin barcha gorutinlarni ehtiyotkorlik bilan to'xtatish. - Biz yaratish orqali klasterga kirishni ta'minlaymiz
clientset
. - Ishga tushirish
NamespaceController
, unda bizning barcha mantiqimiz joylashgan bo'ladi.
Endi biz mantiq uchun asosga muhtojmiz va bizning holatlarimizda bu aytilgan NamespaceController
:
// NamespaceController ΡΠ»Π΅Π΄ΠΈΡ ΡΠ΅ΡΠ΅Π· Kubernetes API Π·Π° ΠΈΠ·ΠΌΠ΅Π½Π΅Π½ΠΈΡΠΌΠΈ
// Π² ΠΏΡΠΎΡΡΡΠ°Π½ΡΡΠ²Π°Ρ
ΠΈΠΌΠ΅Π½ ΠΈ ΡΠΎΠ·Π΄Π°Π΅Ρ RoleBinding Π΄Π»Ρ ΠΊΠΎΠ½ΠΊΡΠ΅ΡΠ½ΠΎΠ³ΠΎ namespace.
type NamespaceController struct {
namespaceInformer cache.SharedIndexInformer
kclient *kubernetes.Clientset
}
// NewNamespaceController ΡΠΎΠ·Π΄Π°Π΅Ρ Π½ΠΎΠ²ΡΠΉ NewNamespaceController
func NewNamespaceController(kclient *kubernetes.Clientset) *NamespaceController {
namespaceWatcher := &NamespaceController{}
// Π‘ΠΎΠ·Π΄Π°Π΅ΠΌ ΠΈΠ½ΡΠΎΡΠΌΠ΅Ρ Π΄Π»Ρ ΡΠ»Π΅ΠΆΠ΅Π½ΠΈΡ Π·Π° Namespaces
namespaceInformer := cache.NewSharedIndexInformer(
&cache.ListWatch{
ListFunc: func(options metav1.ListOptions) (runtime.Object, error) {
return kclient.Core().Namespaces().List(options)
},
WatchFunc: func(options metav1.ListOptions) (watch.Interface, error) {
return kclient.Core().Namespaces().Watch(options)
},
},
&v1.Namespace{},
3*time.Minute,
cache.Indexers{cache.NamespaceIndex: cache.MetaNamespaceIndexFunc},
)
namespaceInformer.AddEventHandler(cache.ResourceEventHandlerFuncs{
AddFunc: namespaceWatcher.createRoleBinding,
})
namespaceWatcher.kclient = kclient
namespaceWatcher.namespaceInformer = namespaceInformer
return namespaceWatcher
}
(
Bu erda biz konfiguratsiya qilamiz SharedIndexInformer
, bu samarali (kesh yordamida) nomlar bo'shliqlarida o'zgarishlarni kutadi (axborotchilar haqida ko'proq maqolada o'qing"EventHandler
ma'lumot beruvchiga, shuning uchun nom maydoni qo'shganda (Namespace
) funksiya chaqiriladi createRoleBinding
.
Keyingi qadam bu funktsiyani aniqlashdir createRoleBinding
:
func (c *NamespaceController) createRoleBinding(obj interface{}) {
namespaceObj := obj.(*v1.Namespace)
namespaceName := namespaceObj.Name
roleBinding := &v1beta1.RoleBinding{
TypeMeta: metav1.TypeMeta{
Kind: "RoleBinding",
APIVersion: "rbac.authorization.k8s.io/v1beta1",
},
ObjectMeta: metav1.ObjectMeta{
Name: fmt.Sprintf("ad-kubernetes-%s", namespaceName),
Namespace: namespaceName,
},
Subjects: []v1beta1.Subject{
v1beta1.Subject{
Kind: "Group",
Name: fmt.Sprintf("ad-kubernetes-%s", namespaceName),
},
},
RoleRef: v1beta1.RoleRef{
APIGroup: "rbac.authorization.k8s.io",
Kind: "ClusterRole",
Name: "edit",
},
}
_, err := c.kclient.Rbac().RoleBindings(namespaceName).Create(roleBinding)
if err != nil {
log.Println(fmt.Sprintf("Failed to create Role Binding: %s", err.Error()))
} else {
log.Println(fmt.Sprintf("Created AD RoleBinding for Namespace: %s", roleBinding.Name))
}
}
(
Biz nom maydonini olamiz obj
va uni ob'ektga aylantiring Namespace
. Keyin aniqlaymiz RoleBinding
, boshida aytib o'tilgan YAML fayliga asoslanib, taqdim etilgan ob'ektdan foydalangan holda Namespace
va yaratish RoleBinding
. Nihoyat, biz yaratish muvaffaqiyatli bo'lganligini qayd qilamiz.
Belgilanishi kerak bo'lgan oxirgi funktsiya Run
:
// Run Π·Π°ΠΏΡΡΠΊΠ°Π΅Ρ ΠΏΡΠΎΡΠ΅ΡΡ ΠΎΠΆΠΈΠ΄Π°Π½ΠΈΡ ΠΈΠ·ΠΌΠ΅Π½Π΅Π½ΠΈΠΉ Π² ΠΏΡΠΎΡΡΡΠ°Π½ΡΡΠ²Π°Ρ
ΠΈΠΌΡΠ½
// ΠΈ Π΄Π΅ΠΉΡΡΠ²ΠΈΡ Π² ΡΠΎΠΎΡΠ²Π΅ΡΡΡΠ²ΠΈΠΈ Ρ ΡΡΠΈΠΌΠΈ ΠΈΠ·ΠΌΠ΅Π½Π΅Π½ΠΈΡΠΌΠΈ.
func (c *NamespaceController) Run(stopCh <-chan struct{}, wg *sync.WaitGroup) {
// ΠΠΎΠ³Π΄Π° ΡΡΠ° ΡΡΠ½ΠΊΡΠΈΡ Π·Π°Π²Π΅ΡΡΠ΅Π½Π°, ΠΏΠΎΠΌΠ΅ΡΠΈΠΌ ΠΊΠ°ΠΊ Π²ΡΠΏΠΎΠ»Π½Π΅Π½Π½ΡΡ
defer wg.Done()
// ΠΠ½ΠΊΡΠ΅ΠΌΠ΅Π½ΡΠΈΡΡΠ΅ΠΌ wait group, Ρ.ΠΊ. ΡΠΎΠ±ΠΈΡΠ°Π΅ΠΌΡΡ Π²ΡΠ·Π²Π°ΡΡ goroutine
wg.Add(1)
// ΠΡΠ·ΡΠ²Π°Π΅ΠΌ goroutine
go c.namespaceInformer.Run(stopCh)
// ΠΠΆΠΈΠ΄Π°Π΅ΠΌ ΠΏΠΎΠ»ΡΡΠ΅Π½ΠΈΡ ΡΡΠΎΠΏ-ΡΠΈΠ³Π½Π°Π»Π°
<-stopCh
}
(
Mana biz gaplashamiz WaitGroup
biz goroutinni ishga tushiramiz va keyin qo'ng'iroq qilamiz namespaceInformer
, bu avvalroq aniqlangan. To'xtash signali kelganda, u funktsiyani tugatadi, xabar bering WaitGroup
, bu endi bajarilmaydi va bu funktsiya o'chadi.
Ushbu bayonotni Kubernetes klasterida yaratish va ishga tushirish haqida ma'lumotni quyidagi sahifada topishingiz mumkin
Bu yaratuvchi operator uchun RoleBinding
qachon Namespace
Kubernetes klasterida tayyor.
Manba: www.habr.com