<!-- 
RSS generated by JIRA (9.4.5#940005-sha1:e3094934eac4fd8653cf39da58f39364fb9cc7c1) at Sat Feb 10 06:04:33 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>Akraino JIRA</title>
    <link>https://jira.akraino.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>9.4.5</version>
        <build-number>940005</build-number>
        <build-date>11-04-2023</build-date>
    </build-info>


<item>
            <title>[REC-33] pod health check</title>
                <link>https://jira.akraino.org/browse/REC-33</link>
                <project id="10202" key="REC">Radio Edge Cloud</project>
                    <description>&lt;p&gt;This test is to check the health of K8s PODs. Two types of health checks can be performed:&lt;/p&gt;
&lt;ol&gt;
	&lt;li&gt;Liveness Test&lt;/li&gt;
	&lt;li&gt;Readiness Test&lt;/li&gt;
&lt;/ol&gt;


&lt;p&gt;For (1), a &lt;font color=&quot;#333333&quot;&gt;liveness probe will check if the container which is configured in the POD&#160;is still running.&#160;&lt;/font&gt;&lt;font color=&quot;#333333&quot;&gt;If the liveness probe fails, the kubelet will kill&#160;the container and re-start the container&lt;/font&gt;&lt;/p&gt;

&lt;p&gt;&lt;font color=&quot;#333333&quot;&gt;For (2), a &lt;/font&gt;&lt;font color=&quot;#333333&quot;&gt;readiness probe will determine if a container is ready to&#160;service requests. If the readiness probe fails, the endpoints&#160;controller will ensure that&#160;the container has its IP address removed from the&#160;endpoints of all services. A readiness probe can be used to signal to the&#160;endpoints controller that even though a container is running, it should not&#160;receive any traffic from a proxy. &lt;/font&gt;&lt;/p&gt;</description>
                <environment></environment>
        <key id="10602">REC-33</key>
            <summary>pod health check</summary>
                <type id="10003" iconUrl="https://jira.akraino.org/secure/viewavatar?size=xsmall&amp;avatarId=10316&amp;avatarType=issuetype">Sub-task</type>
                            <parent id="10600">REC-31</parent>
                                    <priority id="3" iconUrl="https://jira.akraino.org/images/icons/priorities/medium.svg">Medium</priority>
                        <status id="3" iconUrl="https://jira.akraino.org/images/icons/statuses/inprogress.png" description="This issue is being actively worked on at the moment by the assignee.">In Progress</status>
                    <statusCategory id="4" key="indeterminate" colorName="inprogress"/>
                                    <resolution id="-1">Unresolved</resolution>
                                        <assignee username="indubuddi24">Indumathi Buddi</assignee>
                                    <reporter username="dd7022">Deepak Kataria</reporter>
                        <labels>
                    </labels>
                <created>Mon, 26 Aug 2019 18:15:05 +0000</created>
                <updated>Tue, 22 Oct 2019 16:03:05 +0000</updated>
                                                                                <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                                                                <comments>
                            <comment id="10817" author="indubuddi24" created="Tue, 22 Oct 2019 16:01:20 +0000"  >&lt;p&gt;&lt;a href=&quot;https://gerrit.akraino.org/r/#/c/ta/cloudtaf/+/1809/2/testcases/basic_func_tests/tc_002_pod_health_check.py&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://gerrit.akraino.org/r/#/c/ta/cloudtaf/+/1809/2/testcases/basic_func_tests/tc_002_pod_health_check.py&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;</comment>
                            <comment id="10806" author="dd7022" created="Mon, 21 Oct 2019 17:36:05 +0000"  >&lt;p&gt;Indu committed code and it is under review.&lt;/p&gt;</comment>
                            <comment id="10708" author="dd7022" created="Fri, 18 Oct 2019 17:41:25 +0000"  >&lt;p&gt;Indu completed automation. She will commit code to-day (10/18/19).&lt;/p&gt;</comment>
                            <comment id="10697" author="dd7022" created="Wed, 16 Oct 2019 17:39:33 +0000"  >&lt;p&gt;This is work in progress. Indu will try to test this today (10/16/19).&lt;/p&gt;</comment>
                            <comment id="10687" author="dd7022" created="Tue, 15 Oct 2019 17:43:51 +0000"  >&lt;p&gt;Indu is working on automation, since aknode82 is back up now.&lt;/p&gt;</comment>
                            <comment id="10677" author="dd7022" created="Mon, 14 Oct 2019 17:37:21 +0000"  >&lt;p&gt;Manual testing is complete, and test automation is in progress.&lt;/p&gt;</comment>
                            <comment id="10670" author="dd7022" created="Fri, 11 Oct 2019 17:40:35 +0000"  >&lt;p&gt;This is still in progress.&lt;/p&gt;</comment>
                            <comment id="10658" author="dd7022" created="Thu, 10 Oct 2019 17:35:29 +0000"  >&lt;p&gt;This continues to be in progress.&lt;/p&gt;</comment>
                            <comment id="10645" author="dd7022" created="Wed, 9 Oct 2019 18:37:58 +0000"  >&lt;p&gt;Indu is working on automating this with ROBOT, in progress&lt;/p&gt;</comment>
                            <comment id="10636" author="dd7022" created="Tue, 8 Oct 2019 17:35:14 +0000"  >&lt;p&gt;Indu has completed manual testing and is automating with ROBOT.&lt;/p&gt;</comment>
                            <comment id="10624" author="dd7022" created="Fri, 4 Oct 2019 17:40:08 +0000"  >&lt;p&gt;Indu created POD with readiness test and is manually&#160;testing on OE2 cluster. She will automate tests as next step.&lt;/p&gt;</comment>
                            <comment id="10613" author="dd7022" created="Thu, 3 Oct 2019 17:48:11 +0000"  >&lt;p&gt;No update on this.&lt;/p&gt;</comment>
                            <comment id="10596" author="dd7022" created="Wed, 2 Oct 2019 17:35:47 +0000"  >&lt;p&gt;No update on this.&lt;/p&gt;</comment>
                            <comment id="10591" author="dd7022" created="Tue, 1 Oct 2019 19:14:55 +0000"  >&lt;p&gt;No update on this.&lt;/p&gt;</comment>
                            <comment id="10565" author="dd7022" created="Thu, 26 Sep 2019 17:36:29 +0000"  >&lt;p&gt;No update on this.&lt;/p&gt;</comment>
                            <comment id="10555" author="dd7022" created="Wed, 25 Sep 2019 17:36:35 +0000"  >&lt;p&gt;No update on this.&lt;/p&gt;</comment>
                            <comment id="10537" author="dd7022" created="Thu, 19 Sep 2019 17:40:06 +0000"  >&lt;p&gt;No update on this since OE1 cluster was not available. OE1 is back up today, Indu will look into this after addressing review comments on &lt;a href=&quot;https://jira.akraino.org/browse/REC-11&quot; title=&quot;Creating and testing Namespaces&quot; class=&quot;issue-link&quot; data-issue-key=&quot;REC-11&quot;&gt;&lt;del&gt;REC-11&lt;/del&gt;&lt;/a&gt;, &lt;a href=&quot;https://jira.akraino.org/browse/REC-13&quot; title=&quot;Creating and testing Services&quot; class=&quot;issue-link&quot; data-issue-key=&quot;REC-13&quot;&gt;REC-13&lt;/a&gt;, &lt;a href=&quot;https://jira.akraino.org/browse/REC-34&quot; title=&quot;test registry&quot; class=&quot;issue-link&quot; data-issue-key=&quot;REC-34&quot;&gt;REC-34&lt;/a&gt; and &lt;a href=&quot;https://jira.akraino.org/browse/REC-35&quot; title=&quot;file check&quot; class=&quot;issue-link&quot; data-issue-key=&quot;REC-35&quot;&gt;REC-35&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="10526" author="dd7022" created="Wed, 18 Sep 2019 17:36:53 +0000"  >&lt;p&gt;Indu will move to OE1 to continue testing. She has access to service endpoints now.&lt;/p&gt;</comment>
                            <comment id="10518" author="dd7022" created="Tue, 17 Sep 2019 17:36:11 +0000"  >&lt;p&gt;No update on this. Will start working on this to-day (9/17).&lt;/p&gt;</comment>
                            <comment id="10504" author="dd7022" created="Mon, 16 Sep 2019 17:36:19 +0000"  >&lt;p&gt;No update on this&lt;/p&gt;</comment>
                            <comment id="10493" author="dd7022" created="Fri, 13 Sep 2019 17:41:44 +0000"  >&lt;p&gt;Indu did not have a chance to work on this. She will create a POD with Readiness Test.&lt;/p&gt;</comment>
                            <comment id="10464" author="dd7022" created="Mon, 9 Sep 2019 17:39:21 +0000"  >&lt;p&gt;No update on this.&lt;/p&gt;</comment>
                            <comment id="10454" author="dd7022" created="Thu, 5 Sep 2019 17:54:45 +0000"  >&lt;p&gt;Sonobuoy is already doing Liveness Test, Indu confirms. Indu is exploring Readiness Test, she should look at the Service Watcher in REC, to figure out the Readiness test case&lt;/p&gt;</comment>
                            <comment id="10440" author="dd7022" created="Wed, 4 Sep 2019 17:50:20 +0000"  >&lt;p&gt;Indu to check support for Liveness Test in Sonobuoy; Indu to do Readiness Test using DANM endpoint controller as suggested by Levente&lt;/p&gt;</comment>
                            <comment id="10430" author="levovar" created="Wed, 4 Sep 2019 12:25:21 +0000"  >&lt;p&gt;considering this is basic K8s functionality, isn&apos;t it covered by sounoboy or some existing conformance tests?&lt;/p&gt;

&lt;p&gt;what is REC specific related functionality and could be tested is the second, related to readyness probes.&lt;/p&gt;

&lt;p&gt;you remember DANM supports K8s Services for multiple interfaces. in this case it is DANM who is responsible to creating, and deleting the Endpoints of a Service.&lt;/p&gt;

&lt;p&gt;&quot;&#160;If the readiness probe fails, the endpoints&#160;controller will ensure that&#160;the container has its IP address removed from the&#160;endpoints of all services. A readiness probe can be used to signal to the&#160;endpoints controller that even though a container is running, it should not&#160;receive any traffic from a proxy.&quot; -&amp;gt; this functionality could be tested with multi-NIC Services, managed by DANM endpoint controller&lt;/p&gt;</comment>
                            <comment id="10418" author="dd7022" created="Tue, 3 Sep 2019 17:33:49 +0000"  >&lt;p&gt;Indu is working on 2 types of tests. She will test manually and then automate with ROBOT.&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                        <customfield id="customfield_10000" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                    <customfield id="customfield_10105" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i001ev:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                    </customfields>
    </item>
</channel>
</rss>