# Elastic Cloud On kubernetes

**URL:** <https://discuss.elastic.co/t/elastic-cloud-on-kubernetes/247484>\
**Category:** Elastic Cloud on Kubernetes (ECK)\
**Created:** [September 4, 2020, 6:24am UTC](https://discuss.elastic.co/t/elastic-cloud-on-kubernetes/247484 "2020-09-04T06:24:48Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![Vineeth\_varma](https://avatars.discourse-cdn.com/v4/letter/v/45deac/32.png) [@Vineeth\_varma](https://discuss.elastic.co/u/Vineeth_varma)\
**Post date:** [September 4, 2020, 6:24am UTC](https://discuss.elastic.co/t/elastic-cloud-on-kubernetes/247484/1 "2020-09-04T06:24:48Z")

</div>

Hi ..,  
I am giving a try on Elastic cloud on Kubernetes, I have deployed the operator, Elasticsearch and Kibana. Everything is up and running fine.  
Now I want to implement openid connect to kibana using Keycloak, On doing this Do I need any licence or basic licence is sufficient.  
Because, We set up Elasticsearch (version 7.8.0) with an OpenID Connect "oidc" realm with Keycloak as provider. We called the realm "oidc1":  
[...]  
xpack.security.authc.realms.oidc.oidc1:  
claims.principal: name  
op.authorization\_endpoint: [https://keycloak.text/auth/realms/oidc1/protocol/openid-connect/auth](https://keycloak.text/auth/realms/oidc1/protocol/openid-connect/auth)  
op.endsession\_endpoint: [https://keycloak.text/auth/realms/oidc1/protocol/openid-connect/logout](https://keycloak.text/auth/realms/oidc1/protocol/openid-connect/logout)  
op.issuer: [https://keycloak.text/auth/realms/oidc1](https://keycloak.text/auth/realms/oidc1)  
op.jwkset\_path: [https://keycloak.text/auth/realms/oidc1/protocol/openid-connect/certs](https://keycloak.text/auth/realms/oidc1/protocol/openid-connect/certs)  
op.token\_endpoint: [https://keycloak.text/auth/realms/oidc1/protocol/openid-connect/auth](https://keycloak.text/auth/realms/oidc1/protocol/openid-connect/auth)  
op.userinfo\_endpoint: [https://keycloak.text/auth/realms/oidc1/protocol/openid-connect/userinfo](https://keycloak.text/auth/realms/oidc1/protocol/openid-connect/userinfo)  
order: 0  
rp.client\_id: kibana  
rp.post\_logout\_redirect\_uri: [https://ip-removed](https://ip-removed):port/logged\_out  
rp.redirect\_uri: [https://ip-removed](https://ip-removed):port/api/security/oidc/callback  
rp.response\_type: code  
xpack.security.authc.token.enabled: true

# The "rp.client\_secret" is injected into keystore from secret.

To make Kibana (version 7.8.0) use this OpenId Connect realm we added to the Kibana config:  
xpack.security.authc.providers:  
basic.basic1:  
order: 1  
oidc.keycloak:  
order: 0  
realm: oidc1

After configuring all this we experienced the following issues:

- Kibana correctly shows the login selections: "Login with oidc/oidc1" and "Login with Elasticsearch" as expected
- Choosing "Log in with oidc/oidc1" it is not redirting to keycloak... It is giving me authorization issue.

In the Elasticsearch, kibana logs there is literally nothing(!) regarding this oidc login.

Help is really appreciated.

Thanks,  
VIneeth.

---

<div class="post-metadata">

**Author:** ![Vineeth\_varma](https://avatars.discourse-cdn.com/v4/letter/v/45deac/32.png) [@Vineeth\_varma](https://discuss.elastic.co/u/Vineeth_varma)\
**Post date:** [September 7, 2020, 5:45am UTC](https://discuss.elastic.co/t/elastic-cloud-on-kubernetes/247484/2 "2020-09-07T05:45:05Z")

</div>

Is anybody there to help me on this?

---

<div class="post-metadata">

**Author:** ![pebrc](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pebrc/32/101790_2.png) [@pebrc](https://discuss.elastic.co/u/pebrc)\
**Post date:** [September 7, 2020, 7:49am UTC](https://discuss.elastic.co/t/elastic-cloud-on-kubernetes/247484/3 "2020-09-07T07:49:29Z")

</div>

Can you be a bit more specific about the error you are seeing?

Also if you put your configuration examples into triple backticks ``` they will be properly formatted and this will make it much easier to spot any mistakes (especially given that YAML is whitespace sensitive)

---

<div class="post-metadata">

**Author:** ![Vineeth\_varma](https://avatars.discourse-cdn.com/v4/letter/v/45deac/32.png) [@Vineeth\_varma](https://discuss.elastic.co/u/Vineeth_varma)\
**Post date:** [September 8, 2020, 7:30am UTC](https://discuss.elastic.co/t/elastic-cloud-on-kubernetes/247484/4 "2020-09-08T07:30:36Z")

</div>

![image](https://us1.discourse-cdn.com/elastic/original/3X/d/f/df3727d766fad579dc09828173c5df6effadcce2.png)

---

<div class="post-metadata">

**Author:** ![Vineeth\_varma](https://avatars.discourse-cdn.com/v4/letter/v/45deac/32.png) [@Vineeth\_varma](https://discuss.elastic.co/u/Vineeth_varma)\
**Post date:** [September 8, 2020, 7:31am UTC](https://discuss.elastic.co/t/elastic-cloud-on-kubernetes/247484/5 "2020-09-08T07:31:59Z")

</div>

I have verified for oidc to unable, we need to have platinum licence right. So may be because of that I am unable to authenticate through oidc.

---

<div class="post-metadata">

**Author:** ![pebrc](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pebrc/32/101790_2.png) [@pebrc](https://discuss.elastic.co/u/pebrc)\
**Post date:** [September 8, 2020, 7:39am UTC](https://discuss.elastic.co/t/elastic-cloud-on-kubernetes/247484/6 "2020-09-08T07:39:05Z")

</div>

Yes SAML and OpenID Connect are Platinum/Enterprise features. We have an overview of all features and their respective license tiers here: [https://www.elastic.co/subscriptions#elastic-stack-security](https://www.elastic.co/subscriptions#elastic-stack-security)

Please note that ECK is only offered in two licensing tiers: Basic (which is free) and Enterprise. [https://www.elastic.co/guide/en/cloud-on-k8s/master/k8s-licensing.html](https://www.elastic.co/guide/en/cloud-on-k8s/master/k8s-licensing.html)

So in order to use OpenID Connect with ECK you would need an Enterprise license.

---

<div class="post-metadata">

**Author:** ![Vineeth\_varma](https://avatars.discourse-cdn.com/v4/letter/v/45deac/32.png) [@Vineeth\_varma](https://discuss.elastic.co/u/Vineeth_varma)\
**Post date:** [September 18, 2020, 6:28am UTC](https://discuss.elastic.co/t/elastic-cloud-on-kubernetes/247484/7 "2020-09-18T06:28:20Z")

</div>

Hi Peter,  
Here,In the ECK documentation I found only for beats, kibana, elasticsearch.  
There is nothing for logstash, But I want to use logstash for my elastic operator. For this do I have to go for standalone logstash or Any other approach you would like to suggest?  
Thank You,  
Vineeth.

---

<div class="post-metadata">

**Author:** ![michael.morello](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/michael.morello/32/47448_2.png) [@michael.morello](https://discuss.elastic.co/u/michael.morello)\
**Post date:** [September 18, 2020, 6:53am UTC](https://discuss.elastic.co/t/elastic-cloud-on-kubernetes/247484/9 "2020-09-18T06:53:55Z")

</div>

Hi,

> [@Vineeth\_varma](#):
>
> There is nothing for logstash, But I want to use logstash for my elastic operator. For this do I have to go for standalone logstash or Any other approach you would like to suggest?

Logstash is not supported by ECK, you can refer to [this documentation](https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-accessing-elastic-services.html) in order to get everything you need to configure it manually.

---

<div class="post-metadata">

**Author:** ![Vineeth\_varma](https://avatars.discourse-cdn.com/v4/letter/v/45deac/32.png) [@Vineeth\_varma](https://discuss.elastic.co/u/Vineeth_varma)\
**Post date:** [October 6, 2020, 9:19am UTC](https://discuss.elastic.co/t/elastic-cloud-on-kubernetes/247484/11 "2020-10-06T09:19:15Z")

</div>

Do elastic operator itself is having any UI to view clusters it is managing, resources etc...,

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [November 4, 2022, 8:12am UTC](https://discuss.elastic.co/t/elastic-cloud-on-kubernetes/247484/12 "2022-11-04T08:12:29Z")

</div>


