<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Qliksense deployment on Kubernetes using QSEoK in Management &amp; Governance</title>
    <link>https://community.qlik.com/t5/Management-Governance/Qliksense-deployment-on-Kubernetes-using-QSEoK/m-p/1721759#M18564</link>
    <description>&lt;P&gt;Hi Members,&lt;/P&gt;&lt;P&gt;We are planning to deploy&amp;nbsp;QSEoK in our cloud platform. In planning/POC stage we are trying to deploy the QSEoK using Helm charts.&lt;/P&gt;&lt;P&gt;We have certain constraint in our environment on k8s platform. Which is creating issues in deployment. I am looking for any help or suggestion on following points.&lt;/P&gt;&lt;P&gt;1.&amp;nbsp;QSEoK requires docker images to be downloaded from&amp;nbsp;qlik-docker-qsefe.bintray.io and dockerHub. In our case we are using artifactory for repository and docker images. How we can force chart to pick images from internal repository. I can see number of images gets deployed in QSEoK&lt;/P&gt;&lt;P&gt;2. We do not have dynamic storage allocation via k8s storage class. We can define pvc/pv/sc to handle it manually. Please suggest how to take this further in values.yaml&amp;nbsp;&lt;/P&gt;&lt;P&gt;engine:&lt;BR /&gt;acceptEULA: "yes"&lt;BR /&gt;persistence:&lt;BR /&gt;enabled: true&lt;BR /&gt;accessMode: ReadWriteMany&lt;BR /&gt;existingClaim: qlik-pvc&lt;/P&gt;&lt;P&gt;please let me know how we can manage global persistence. Thanks&amp;nbsp;&lt;/P&gt;&lt;P&gt;#global:&lt;BR /&gt;# persistence:&lt;BR /&gt;# storageClass: "xyz-qlik"&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Ak&lt;/P&gt;</description>
    <pubDate>Sat, 16 Nov 2024 18:26:57 GMT</pubDate>
    <dc:creator>Robinhood_lko</dc:creator>
    <dc:date>2024-11-16T18:26:57Z</dc:date>
    <item>
      <title>Qliksense deployment on Kubernetes using QSEoK</title>
      <link>https://community.qlik.com/t5/Management-Governance/Qliksense-deployment-on-Kubernetes-using-QSEoK/m-p/1721759#M18564</link>
      <description>&lt;P&gt;Hi Members,&lt;/P&gt;&lt;P&gt;We are planning to deploy&amp;nbsp;QSEoK in our cloud platform. In planning/POC stage we are trying to deploy the QSEoK using Helm charts.&lt;/P&gt;&lt;P&gt;We have certain constraint in our environment on k8s platform. Which is creating issues in deployment. I am looking for any help or suggestion on following points.&lt;/P&gt;&lt;P&gt;1.&amp;nbsp;QSEoK requires docker images to be downloaded from&amp;nbsp;qlik-docker-qsefe.bintray.io and dockerHub. In our case we are using artifactory for repository and docker images. How we can force chart to pick images from internal repository. I can see number of images gets deployed in QSEoK&lt;/P&gt;&lt;P&gt;2. We do not have dynamic storage allocation via k8s storage class. We can define pvc/pv/sc to handle it manually. Please suggest how to take this further in values.yaml&amp;nbsp;&lt;/P&gt;&lt;P&gt;engine:&lt;BR /&gt;acceptEULA: "yes"&lt;BR /&gt;persistence:&lt;BR /&gt;enabled: true&lt;BR /&gt;accessMode: ReadWriteMany&lt;BR /&gt;existingClaim: qlik-pvc&lt;/P&gt;&lt;P&gt;please let me know how we can manage global persistence. Thanks&amp;nbsp;&lt;/P&gt;&lt;P&gt;#global:&lt;BR /&gt;# persistence:&lt;BR /&gt;# storageClass: "xyz-qlik"&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Ak&lt;/P&gt;</description>
      <pubDate>Sat, 16 Nov 2024 18:26:57 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Qliksense-deployment-on-Kubernetes-using-QSEoK/m-p/1721759#M18564</guid>
      <dc:creator>Robinhood_lko</dc:creator>
      <dc:date>2024-11-16T18:26:57Z</dc:date>
    </item>
  </channel>
</rss>

