Get rid of tcpMutex, tlsMutex and ingressClassMutex from integration tests

[programmer04]

Is there an existing issue for this?

• I have searched the existing issues

Problem Statement

Some integration tests require

kubernetes-ingress-controller/test/integration/tcpingress_test.go

Lines 33 to 36 in 09f1e55

	var (
	tcpMutex sync.Mutex
	tlsMutex sync.Mutex
	)

those tests should be migrated to isolated tests. UDP-related tests have been already migrated as a byproduct of fighting with flakes.

Similar situation is for ingressClassMutex.

Also, it's a great opportunity for improvement and cleanups, e.g. usage of assertion helpers from test/integration/isolated/assertion_helpers.go. See UDP corresponding tests for inspiration.

Proposed Solution

• tests are migrated to isolated
• tcpMutex, tlsMutex and ingressClassMutex are no longer needed

Acceptance Criteria

• tests are migrated to isolated
• tcpMutex, tlsMutex and ingressClassMutex are removed

[YiTongG]

Hi ~ I want to help, can you assign this tasks to me?

[programmer04]

Sure @YiTongG, you can try

[LindaSummer]

Hi @programmer04 ,

This issue seems to be inactive for one more month.
I'm a newbie of Kong community and want to make some contribution.

Can this issue be assigned to me?

Best Regards,
Edward

[programmer04]

Please try @LindaSummer, I've assigned it to you. In case of any questions do not hesitate to reach me

[LindaSummer]

I've assigned it to you. In case of any questions do not hesitate to reach me

Hi @programmer04 ,

Thanks very much! 😊
I will try to be familiar with the codebase structure and the testing flow these days.

Best Regards,
Edward