# Fresh instance with Percona XtraDB Cluster Operator v1.8.0 not starting completly under OKD

**URL:** <https://forums.percona.com/t/fresh-instance-with-percona-xtradb-cluster-operator-v1-8-0-not-starting-completly-under-okd/10415>\
**Category:** Percona Operator for MySQL\
**Created:** [May 11, 2021, 9:44am UTC](https://forums.percona.com/t/fresh-instance-with-percona-xtradb-cluster-operator-v1-8-0-not-starting-completly-under-okd/10415 "2021-05-11T09:44:01Z")\
**Posts on this page:** 1\
**Showing post:** 22

<div class="post-metadata">

**Author:** ![Slava\_Sarzhan](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/slava_sarzhan/32/3196_2.png) [@Slava\_Sarzhan](https://forums.percona.com/u/Slava_Sarzhan)\
**Post date:** [October 11, 2021, 5:13pm UTC](https://forums.percona.com/t/fresh-instance-with-percona-xtradb-cluster-operator-v1-8-0-not-starting-completly-under-okd/10415/22 "2021-10-11T17:13:04Z")

</div>

@pavloos Please have a look at this commit [K8SPXC-876 use PublishNotReadyAddresses instead of annotation · percona/percona-xtradb-cluster-operator@808ce22 · GitHub](https://github.com/percona/percona-xtradb-cluster-operator/commit/808ce2262b21abe290c2dbcf8324b54a9a9a824d)

This issue was fixed for 1.10.0. As a workaround you can edit service `kubectl edit svc/${clustername}-pxc-unready` manually and add `publishNotReadyAddresses: true` to the spec.

---

_[View the full topic](https://forums.percona.com/t/fresh-instance-with-percona-xtradb-cluster-operator-v1-8-0-not-starting-completly-under-okd/10415)._